jambay
https://www.waypointproject.io/docs/entrypoint/disable#disab...
https://www.waypointproject.io/docs/entrypoint/disable#disab...
Yes, the plugin architecture is an essential part of Waypoint and we hope to see a large ecosystem of plugins. Rather than focuses exclusively on k8s, Waypoint is designed to center on the build, deploy, release workflow to any platform via plugins. There's a lot of plugins already built-in [1] and the Plugin SDK [2] makes it pretty straight-forward to build new ones.
[1] https://www.waypointproject.io/plugins [2] https://www.waypointproject.io/docs/extending-waypoint
We do hope to have Waypoint as a HashiCorp Cloud offering in the future. Yet we expect the have the core workflows available in open source. There may someday be features in a paid Enterprise edition, similar the approach we've used well with Vault.
https://github.com/hashicorp/waypoint-examples/tree/main/doc...
You don't have to use buildpacks, you could use the Docker plugin with a Dockerfile as in this reactjs example: https://github.com/hashicorp/waypoint-examples/tree/main/doc...
[1] https://www.hashicorp.com/blog/hashicorp-nomad-autoscaling-t...
Disclaimer: I work at HashiCorp in Product Management.
there is going to be a large spectrum of ways to run docker images, and you'll be able to choose bare bones to full-service.
here is a 4min video of cloud foundry next generation runtime diego showing spinning up 300 docker images in under a minute, providing load balancing, health management and aggregated logging: http://www.youtube.com/watch?v=e76a50ZgzxM
james - cloud foundry team
warden has a c server core [2] wrapping cgroups and other features currently on the lmctfy roadmap like network and file system isolation [3]. the current file system isolation uses either aufs or overlayfs depending on the distro/linux version you are using [4]. the network uses namespaces and additional features.
warden also has early/experimental support for centos in addition to ubuntu, although some of the capabilities are degraded. for example, disk isolation uses a less efficient, but still workable copy file system approach.
the client orchestration of warden is currently written in ruby, but there was also a branch started to move that to go [5] that has not been hardened and moved into master.
recently cloudfoundry started using bosh-lite [2] leveraging warden to do full dev environments using linux containers instead of separate linux hosts on many virtual machines from an IaaS provider, which has dramatically reduced the resources and time required to create, develop and use the full system.
[1] https://twitter.com/pnoordhuis [2] https://github.com/cloudfoundry/warden/tree/master/warden/sr... [3] https://github.com/cloudfoundry/warden/blob/master/warden/RE... [4] https://github.com/cloudfoundry/warden/blob/master/warden/RE... [5] https://github.com/cloudfoundry/warden/tree/go
bytes = 100
Should be
bytes[i] = 100
Right or wrong?