11–15 of 15 posts
It looks like this is a renaming and refocusing of Sstampede.io, which was discussed before at https://news.ycombinator.com/item?id=8210100
Earlier quoted context omitted.
A docker container can manage the docker installation on the host. This is done by binding the docker.sock from the host to the container with the following command line argument: `-v /var/run/docker.sock:/var/run/docker.sock`
Of course it can. The question is, why would you want to?
Rancher is packaged as a set of Docker containers. This may seem like inception but we build off of the portability guarantees provided by Docker. This means that the storage and networking services we provide should run anywhere Docker runs.
The source code for this project is mostly in https://github.com/rancherio/cattle at the moment. We will be moving things around quite a bit and in the end we will have a lot of repos that comprise the project. https://github.com/rancherio/rancher serves as a meta-repo that packages up all of the other repos.
I feel like alternatives to all these services exist already. What AWS provides is packaging and integration.
If I want S3, I can use one of several distributed filestores.
If I want EBS, I can use one of several network disk systems.
If I want queues, or distributed K-V stores, or monitoring, etc etc etc, there are solutions coming out of our collective ears.
AWS is an IaaS. People are paying for the service, not the infrastructure.