Live data from Hacker News

Show HN: Hosted Docker-as-a-Service on SSDs for $5

blog.copper.io

101–110 of 133 posts

Re: Show HN: Hosted Docker-as-a-Service on SSDs for $5

#101
post #97
post #68

Earlier quoted context omitted.

The real question is why Sun didn't succeed in leveraging this technology with their implementation of zones.

To be honest - I think it's a timing thing - virtualization wasn't popular initially but VMWare did a great marketing job. Then any hyper-visor became acceptable. Now - VPS-style containers are becoming acceptable. IE: Docker.

Timing is definitely part of it.

Being too early can kill you. If you think your idea is awesome but too early, my advice is to keep trying for as long as it takes. Docker was not my first attempt at solving this particular problem :) [1] [2] [3]

[1] https://bitbucket.org/Foi3GraS/dotcloud-fork/commits/1

[2] https://github.com/dotcloud/cloudlets/commit/0af885a5266fba7...

[3] https://bitbucket.org/dotcloud/vm2vm/commits/2a34438989fbff0...

Re: Show HN: Hosted Docker-as-a-Service on SSDs for $5

#102
post #63

Hi everyone, Docker maintainer here. Here's my list of docker hosting services. Please correct me if I forgot one! I expect this list to get much, much longer in the next couple months. * http://baremetal.io * http://digitalocean.com (not docker-specific but they have a great docker image) * http://orchardup.com * http://rackspace.com (not docker-specific but they have a great docker image) * http://stackdock.com EDI…

The rise of Docker is fascinating. How did you get people to care about it initially? Did everyone immediately see it as a good idea? Congrats.

I learned about it from creack (lead contributor according to github) @ a startup meetup in SF.

Things that impressed me:

1. super passionate

2. he was very receptive and quick at squashing bugs I reported (real or not)

3. docker was super portable (the same across all linux distros)

4. they (the docker team) had real solutions for the long application deployment times that were plaguing me

Everyone seemed to know it would succeed, which is rare around here.

Re: Show HN: Hosted Docker-as-a-Service on SSDs for $5

#103
post #63

Hi everyone, Docker maintainer here. Here's my list of docker hosting services. Please correct me if I forgot one! I expect this list to get much, much longer in the next couple months. * http://baremetal.io * http://digitalocean.com (not docker-specific but they have a great docker image) * http://orchardup.com * http://rackspace.com (not docker-specific but they have a great docker image) * http://stackdock.com EDI…

The rise of Docker is fascinating. How did you get people to care about it initially? Did everyone immediately see it as a good idea? Congrats.

When you are an ops and spend time finding the perfect way to make "redeploying easier than fixing", docker became the answer.

I got to meet the docker team (a lot of french dudes in the team!). Very passionate, technically super sharp, and really fun ! They were interested in my point of view and opinion. Plus, there lead dev knows how to party from what i have seen during a meetup !

Re: Show HN: Hosted Docker-as-a-Service on SSDs for $5

#104
post #86
post #65

Earlier quoted context omitted.

We spent 3 months going door to door, making demos to people I knew were working on similar projects or looking for one. We had a good reputation in the ops and systems engineering community because of our work on dotCloud over the last 6 years. Then we bootstrapped the open-source community with that initial group of 30-50 people willing to federate efforts. By the time the project was leaked on hacker news, the git…

So, hi there. I'd like to invest in you guys, where do I send the cheque? :)

No response yet, hmm. Seriously, guys, I have a $100 bill here with your name on it.

Re: Show HN: Hosted Docker-as-a-Service on SSDs for $5

#106
post #16
post #13

Earlier quoted context omitted.

"You can create a Docker file with some easy steps we’ve created, or you can upload your own Docker file and create an instance from that." Sounds like a yes.

Well, no. A Dockerfile is the build instructions, not the build artifact.

you can commit at any point and ship that via private registry

Re: Show HN: Hosted Docker-as-a-Service on SSDs for $5

#107
One thing that confuses me with Docker is that how do you configure your containers to communicate with each other.

So say I have a fancy Django image, and a fancy Postgres image.

How do I then have the Django one learn of the Postgres one's IP, and then auths (somehow), and then communicates seperately.

Also, the recommended advice for "production" is to mount host directories for the PostgreSQL data directory. Doesn't this rather defeat the point of a container (in that it's self contained), and how does that even work with a DaaS like this? I'm pretty confused. Is there an idiomatic way in which to do this?

Do service registration/discovery things for Docker already exist?

Re: Show HN: Hosted Docker-as-a-Service on SSDs for $5

#108

One thing that confuses me with Docker is that how do you configure your containers to communicate with each other. So say I have a fancy Django image, and a fancy Postgres image. How do I then have the Django one learn of the Postgres one's IP, and then auths (somehow), and then communicates seperately. Also, the recommended advice for "production" is to mount host directories for the PostgreSQL data directory. Does…

> One thing that confuses me with Docker is that how do you configure your containers to communicate with each other.

Docker now supports linking containers together:

http://blog.docker.io/2013/10/docker-0-6-5-links-container-n...

> Also, the recommended advice for "production" is to mount host directories for the PostgreSQL data directory. Doesn't this rather defeat the point of a container (in that it's self contained)

The recommended advice for production is to create a persistent volume with 'docker run -v', and to re-use volumes across containers with 'docker run -volumes-from'.

Mounting directories from the host is supported, but it is a workaround for people who already have production data outside of docker and want to use it as-is. It is not recommended it you can avoid it.

Either way, you're right, it is an exception to the self-contained property of containers. But it is limited to certain directories, and docker guarantees that outside of those directories the changes are isolated. This is similar to the "deny by default" pattern in security. It's more reliable to maintain a whitelist than a blacklist.

Re: Show HN: Hosted Docker-as-a-Service on SSDs for $5

#109
post #86

Earlier quoted context omitted.

So, hi there. I'd like to invest in you guys, where do I send the cheque? :)

No response yet, hmm. Seriously, guys, I have a $100 bill here with your name on it.

I am flattered, but we are already well funded and are not currently looking for new investors. However if you're feeling generous I can point you to a few people who have been making awesome contributions to Docker on their free time. I'm sure they would appreciate donations, or perhaps contract work :)

There are also several startups currently raising money for a business based on docker. This is bigger than any one company!

Re: Show HN: Hosted Docker-as-a-Service on SSDs for $5

#110
post #92
post #80

Earlier quoted context omitted.

So I already use Linux almost exclusively for development, and VMs are not in my workflow at all. It seems bizarre to build a VM to build a container! Like too many levels of yak shaving.

> It seems bizarre to build a VM to build a container! Like too many levels of yak shaving. Perhaps, but you just said: > I have a 32 bit Linux desktop and a Mac and haven't gotten around to installing Docker. At work I have a 64 bit Linux desktop and it seemed to be extremely picky about the kernel version so I gave up. Precisely. Hence VMs, because Vagrant makes it trivial to spin up an instance configured however…

I can see where you're coming from, but my issue is that Docker itself is LESS portable than the applications it's containerizing! It's creating the very problem it's trying to solve. The task I care about isn't to build and deploy a Docker container. It's to build and deploy my app.

I have a beef with build/deploy systems that have bootstrapping problems. For example I'm hearing from people using Chef that they have to freeze the version of Chef, its dependencies, and the Ruby interpreter (or maybe it was Puppet, I don't use either). To me that is just crazy. My code isn't that picky about the versions it needs, and to introduce a deployment tool like that makes things less stable, not more.

Take for example Python -- in my experience it's almost entirely portable because Linux and Mac. And I imagine the same is with node.js, Ruby, PHP, etc. Almost all C libraries you need are portable too. So in my ideal world you would only use a VM when you actually need it for the OS/CPU architecture. I suspect for a lot of people that would be 50-90% the time without a VM, depending on how you like to develop.

I'm working on a chroot-based build system, which in theory will work on Mac and Linux (but not Windows). It does need to solve a versioning problem. Because stuff isn't as portable between Python 2.6 and Python 2.7 on the same OS as it is between Python 2.7 on two different architectures/OSes.

Post reply on HN