4 ms·

Portable AWS-style infrastructure service for Docker

46 points by inakiabt 12y ago

jessaustin 12y ago
The vision seems to be docker on top of rancher on top of docker? Afraid I can't see how this would help? Unless it's just to inspire "yo dawg" Xzibit jokes? b^)
- nacho_weekend 12y ago
  I think it's more in the vein of "manage the docker containers you are deploying with rancher, which is itself another docker container to keep consistent with the entire environment being in docker"
- tokenizerrr 12y ago
  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`
  - xorcist 12y ago
    Of course it can. The question is, why would you want to?
    - mateuszf 12y ago
      Guessing so that installation process is portable and isolated from original host.
    - tokenizerrr 12y ago
      Easy/simple/self-contained installation and portability. Why would you want to run anything at all in docker?
aidos 12y ago
I went to have a snoop around the code but all I can really see is installation files. Genuine question, is this project closed source? I haven't really worked with Docker in anger yet - but I guess I could pull down the files / run it and then take a look inside to see how it works. Is there a link to the original code? Is there a risk that projects are going to start to be released in a way where it's going to take jumping through a couple of hoops to see how they work? I don't want to sound disparaging to the project (it sounds interesting). I was just curious in having a really quick glance at the code to see if it was something I wanted to keep an eye on.
- inakiabt 12y ago
  Seems like some of the source code of different components are here: https://github.com/rancherio https://github.com/rancherio * Agent: https://github.com/rancherio/rancher-agent https://github.com/rancherio/rancher-agent * Cattle: https://github.com/rancherio/cattle https://github.com/rancherio/cattle
k0 12y ago
Looking forward to the Volume Management and Load Balancing features. Keep up the good work.
zemanel 12y ago
Off topic to rancher maybe but how about [a tool for] treating (packaging) docker images as [Debian/rpm] packages, at least persistent images (images that are not one shot jobs) ? Some of the images workflow as deploying/removing from a host, replacing existing images (upgrades), dependency management (app image v1.0 depends on Nginx image v2.0), metadata like OS startup scripts (pg image needs to start on boot) seems to already be covered by apt/rpm and that tools like Ansible/others leverage for deployments in infrastructures.
sciurus 12y ago
Here is a blog post announcing the project: http://www.ibuildthecloud.com/blog/2014/11/11/announcing-rancher-dot-io/ http://www.ibuildthecloud.com/blog/2014/11/11/announcing-ran... It looks like this is a renaming and refocusing of Sstampede.io, which was discussed before at https://news.ycombinator.com/item?id=8210100 https://news.ycombinator.com/item?id=8210100
darren0 12y ago
Chief architect of Rancher here. Rancher.io is in fact completely open source. The intention is that Rancher will run below Docker. Rancher currently wraps Docker but going forward that will no longer be the case. We very much want users to use the native Docker CLI and remote API. 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 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 https://github.com/rancherio/rancher serves as a meta-repo that packages up all of the other repos.
jacques_chester 12y ago
Hi, some obligatory HN nay-saying here. 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.
deleted 12y ago
[deleted]

46 points by inakiabt 12y ago

The vision seems to be docker on top of rancher on top of docker? Afraid I can't see how this would help? Unless it's just to inspire "yo dawg" Xzibit jokes? b^)

nacho_weekend 12y ago
I think it's more in the vein of "manage the docker containers you are deploying with rancher, which is itself another docker container to keep consistent with the entire environment being in docker"
tokenizerrr 12y ago
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`
- xorcist 12y ago
  Of course it can. The question is, why would you want to?
  - mateuszf 12y ago
    Guessing so that installation process is portable and isolated from original host.
  - tokenizerrr 12y ago
    Easy/simple/self-contained installation and portability. Why would you want to run anything at all in docker?

aidos 12y ago

I went to have a snoop around the code but all I can really see is installation files. Genuine question, is this project closed source? I haven't really worked with Docker in anger yet - but I guess I could pull down the files / run it and then take a look inside to see how it works. Is there a link to the original code? Is there a risk that projects are going to start to be released in a way where it's going to take jumping through a couple of hoops to see how they work? I don't want to sound disparaging to the project (it sounds interesting). I was just curious in having a really quick glance at the code to see if it was something I wanted to keep an eye on.

inakiabt 12y ago
Seems like some of the source code of different components are here: https://github.com/rancherio https://github.com/rancherio * Agent: https://github.com/rancherio/rancher-agent https://github.com/rancherio/rancher-agent * Cattle: https://github.com/rancherio/cattle https://github.com/rancherio/cattle

k0 12y ago

Looking forward to the Volume Management and Load Balancing features. Keep up the good work.

zemanel 12y ago

Off topic to rancher maybe but how about [a tool for] treating (packaging) docker images as [Debian/rpm] packages, at least persistent images (images that are not one shot jobs) ? Some of the images workflow as deploying/removing from a host, replacing existing images (upgrades), dependency management (app image v1.0 depends on Nginx image v2.0), metadata like OS startup scripts (pg image needs to start on boot) seems to already be covered by apt/rpm and that tools like Ansible/others leverage for deployments in infrastructures.

sciurus 12y ago

Here is a blog post announcing the project: http://www.ibuildthecloud.com/blog/2014/11/11/announcing-rancher-dot-io/ http://www.ibuildthecloud.com/blog/2014/11/11/announcing-ran... It looks like this is a renaming and refocusing of Sstampede.io, which was discussed before at https://news.ycombinator.com/item?id=8210100 https://news.ycombinator.com/item?id=8210100

darren0 12y ago

Chief architect of Rancher here. Rancher.io is in fact completely open source. The intention is that Rancher will run below Docker. Rancher currently wraps Docker but going forward that will no longer be the case. We very much want users to use the native Docker CLI and remote API. 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 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 https://github.com/rancherio/rancher serves as a meta-repo that packages up all of the other repos.

jacques_chester 12y ago

Hi, some obligatory HN nay-saying here. 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.

deleted 12y ago

[deleted]