About The Alternatives - Chef, Ansible, Puppet
Ansible does decent job on AWS for cloud provisioning, but has been slow to get parity with AWS updates/feaptures, such as EKS, that was half year too late, where Terraform was there day zero. Pull based change configs like Chef and Puppet are not suitable for orchestration and…
Similarities DC/OS (Mesosphere), Chef, and Puppet
This is great insight, and can see similarities with other platforms that might be opinionated. In case of classic change config, they resisted the cloud and container renaissance, and struggle to find their place.
For Windows, one way is to enable access to TCP w/o TLS (insecure), which is not enabled by default with Docker-Desktop (previously Docker-for-Windows).
The info from your posted Windows link will never work as you cannot mount Unix sockets, for Windows has no support for Unix sockets, as it is, well, Windows. Windows has support for Named Pipes or TCP.
I was wondering if there were good examples of more complex data structures, or how would I go about having an object that maintains it’s own state, where you call methods to mutate the state, like addItem(), deleteItem().
Building base images makes sense, replacing a Dockerfile crafted images, or layered (Lego-like) stacked image, with fully baked golden image (packer, ansible-container) is a throw-back to older pets days (pets vs. cattles metaphor) when sys admins maintained image libraries.
Thanks for the blog post, really nice. Three things: