Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: Is it just me or why does Docker suck so much?

news.ycombinator.com

Post reply on HN
Print view View original

21–30 of 85 posts

Re: Ask HN: Is it just me or why does Docker suck so much?

#21

Post by ajdecon »

ironchef wrote: post #9
est wrote: post #5

Earlier quoted context omitted.

some of us use HOSTS to write config e.g. 10.0.12.34 mysql_host This allows some degree of flexbility 1. boot up new instances quickly as long as HOSTS is correct 2. Don't have to hard-code actual mysql server IPs. 3. Make mysql master/slave failover much easier.

I think most folks doing devops end up using things more like zookeeper, consul, etc. instead to perform the above as opposed to hosts.

Remember you may have to deploy third-party processes as well as apps whose code you control. Most existing software uses OS-standard APIs for doing things like resolving hosts, and you can't just point it at a path in zk. That means running a DNS server or configuring /etc/hosts.

Re: Ask HN: Is it just me or why does Docker suck so much?

#23

Post by rabino »

lgbr wrote: post #13

Setting up a private repository is a PITA? It's one command: docker run -p 5000:5000 registry Want to back it with S3 or another storage provider? It's still one command: docker run -e SETTINGS_FLAVOR=s3 -e AWS_BUCKET=acme-docker -e STORAGE_PATH=/registry -e AWS_KEY=AKIAHSHB43HS3J92MXZ -e AWS_SECRET=xdDowwlK7TJajV1Y7EoOZrmuPEJlHYcNP2k4j49T -e SEARCH_BACKEND=sqlalchemy -p 5000:5000 registry What's so pain in the ass a…

did you just post your s3 secret key?

Re: Ask HN: Is it just me or why does Docker suck so much?

#24

Post by corford »

emeraldd wrote: post #18
corford wrote: post #10

I've been waiting for the hype to die down a bit and for the project to stabilise before properly playing with it but, from the outside looking in, I must admit I struggle to see how it's gaining as much attention as it is. I can see the advantage for dev boxes where a developer might want to setup a load of containers on their machine to emulate a staging or production environment. But I don't really understand why…

That works if you have physical access to the machine/vm. What about EC2? Linode? Digital Ocean? etc.

Fair point. I guess for serious stuff I just find it bizarre that you'd want to run a load of containers in a vm (rather than just spooling up additional dropelts or linode instances). For non 'weekend project' stuff, surely it's cheaper and more efficient to lease a dedicated server and stick your own vms on that?

Re: Ask HN: Is it just me or why does Docker suck so much?

#25

Post by tethra »

rabino wrote: post #23
lgbr wrote: post #13

Setting up a private repository is a PITA? It's one command: docker run -p 5000:5000 registry Want to back it with S3 or another storage provider? It's still one command: docker run -e SETTINGS_FLAVOR=s3 -e AWS_BUCKET=acme-docker -e STORAGE_PATH=/registry -e AWS_KEY=AKIAHSHB43HS3J92MXZ -e AWS_SECRET=xdDowwlK7TJajV1Y7EoOZrmuPEJlHYcNP2k4j49T -e SEARCH_BACKEND=sqlalchemy -p 5000:5000 registry What's so pain in the ass a…

did you just post your s3 secret key?

I was wondering, too..

Re: Ask HN: Is it just me or why does Docker suck so much?

#26

Post by shitlord »

rabino wrote: post #23
lgbr wrote: post #13

Setting up a private repository is a PITA? It's one command: docker run -p 5000:5000 registry Want to back it with S3 or another storage provider? It's still one command: docker run -e SETTINGS_FLAVOR=s3 -e AWS_BUCKET=acme-docker -e STORAGE_PATH=/registry -e AWS_KEY=AKIAHSHB43HS3J92MXZ -e AWS_SECRET=xdDowwlK7TJajV1Y7EoOZrmuPEJlHYcNP2k4j49T -e SEARCH_BACKEND=sqlalchemy -p 5000:5000 registry What's so pain in the ass a…

did you just post your s3 secret key?

According to google, this isn't the first time that key was posted. It's here[1] too.

[1]: https://pypi.python.org/pypi/docker-registry/0.7.3

Re: Ask HN: Is it just me or why does Docker suck so much?

#27

Post by Zikes »

diggan wrote: post #14
est wrote: post #5

Earlier quoted context omitted.

some of us use HOSTS to write config e.g. 10.0.12.34 mysql_host This allows some degree of flexbility 1. boot up new instances quickly as long as HOSTS is correct 2. Don't have to hard-code actual mysql server IPs. 3. Make mysql master/slave failover much easier.

Regarding number two, you'll just link your containers together with docker. See https://docs.docker.com/userguide/dockerlinks/ It seems that most issues OP have is mostly because misunderstanding or lack of knowledge.

What if the mysql server isn't in a docker container or even on the same machine?

Re: Ask HN: Is it just me or why does Docker suck so much?

#28

Post by kachnuv_ocasek »

rabino wrote: post #23
lgbr wrote: post #13

Setting up a private repository is a PITA? It's one command: docker run -p 5000:5000 registry Want to back it with S3 or another storage provider? It's still one command: docker run -e SETTINGS_FLAVOR=s3 -e AWS_BUCKET=acme-docker -e STORAGE_PATH=/registry -e AWS_KEY=AKIAHSHB43HS3J92MXZ -e AWS_SECRET=xdDowwlK7TJajV1Y7EoOZrmuPEJlHYcNP2k4j49T -e SEARCH_BACKEND=sqlalchemy -p 5000:5000 registry What's so pain in the ass a…

did you just post your s3 secret key?

No, it's an example from the readme: https://github.com/docker/docker-registry#quick-start

Re: Ask HN: Is it just me or why does Docker suck so much?

#29

Post by Matheo05 »

rabino wrote: post #23
lgbr wrote: post #13

Setting up a private repository is a PITA? It's one command: docker run -p 5000:5000 registry Want to back it with S3 or another storage provider? It's still one command: docker run -e SETTINGS_FLAVOR=s3 -e AWS_BUCKET=acme-docker -e STORAGE_PATH=/registry -e AWS_KEY=AKIAHSHB43HS3J92MXZ -e AWS_SECRET=xdDowwlK7TJajV1Y7EoOZrmuPEJlHYcNP2k4j49T -e SEARCH_BACKEND=sqlalchemy -p 5000:5000 registry What's so pain in the ass a…

did you just post your s3 secret key?

In fact, it comes from the Docker GitHub page https://github.com/docker/docker-registry/tree/master

Re: Ask HN: Is it just me or why does Docker suck so much?

#30

Post by jasode »

corford wrote: post #10

I've been waiting for the hype to die down a bit and for the project to stabilise before properly playing with it but, from the outside looking in, I must admit I struggle to see how it's gaining as much attention as it is. I can see the advantage for dev boxes where a developer might want to setup a load of containers on their machine to emulate a staging or production environment. But I don't really understand why…

>What's wrong with setting up kvm "gold" images for your various server types (db server, redis instance, ha proxy server etc.) and then just dd'ing those images to host machines and using ansible/puppet/chef to do any final role configuration on first boot?

You're leaving out the other attractive aspects of Docker/containers: performance, lower cpu utilization, instant spin up, less disk space, etc. Those factors lead to higher density of images on servers. Puppet/Chef + hypervisors can't compete with those particular factors.

In summary:

Containers have less isolation, but can be more densely packed. VMs have more isolation, but less densely packed.

The 2 technologies have different tradeoffs and economics.

Post reply on HN