3 ms·
I'm stating to really get into containers. They make sense and can keep sane environments; keeping you away from dependency hell (at the expense of potential se
by djsumdog 10y ago
I'm stating to really get into containers. They make sense and can keep sane environments; keeping you away from dependency hell (at the expense of potential security issues if you don't have tools that regularly scan and tell you when packages within containers have security issues).
Unfortunately, the orchestration formats are all over the place. Kubernetes, DC/OS and Docker-compose all have their own json schema. DC/OS doesn't even support docker container volumes. Rancher can take docker-compose, and it looks like it can deploy those apps on K8s/DCOS, however I haven't messed with it enough to see if that actually works.
Rkt just adds even another container format. What once seemed like a nice one-stop isolated application that you could run anywhere is becoming more complicated and more tightly coupled to the underlying container engine and orchestration system you chose to use.
- philips 10y agorkt is not a new container format. It is a thing that executes container images and implements all of the current formats including OCI, Docker Images, and appc. No other container engine can download and execute all of those formats today. For users using rkt + Kubernetes they can execute Docker Images just like normal. https://coreos.com/rkt/docs/latest/running-docker-images.html https://coreos.com/rkt/docs/latest/running-docker-images.htm...
- brndnmtthws 10y agoDC/OS most certainly supports Docker volumes. What made you think it doesn't?
- brndnmtthws 10y agoOr perhaps you're referring to the data volume containers. Regardless, you can pass arbitrary arguments to the Docker daemon if you choose.