Ask HN: Is it just me or why does Docker suck so much? • Hacker News Board

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

#81

Post by shykes » Wed, Aug 13, 2014, 7:33 PM UTC

antocv wrote: post #65

ninkendo wrote: post #60

After having used docker for "real" things for the past 8 months or so, I definitely agree with you that it kinda sucks. Docker's strengths come from the workflow you get to use when you use it... "Run /bin/bash in ubuntu" and it just works. For developers that's great. For a backend that does the heavy lifting for you when you're developing a lot of operations automation (like a PaaS), it starts to break down. Just…

I ran into dm issues too, something with grsecurity stopping a bruteforce. Oh and that ADD this /that will chown 0:0 that. Come on.

Hi, the reason ADD applies a `chown 0:0` is to avoid applying the uid/gid of the files on the source system, which could be anything and would introduce a side effect in your application's build.

There is a pull request for letting you set a the destination uid/gid determinastically, which is the right way to do it.

Just a reminder that we accept bug reports and patches :)

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

#82

Post by bnjs » Fri, Aug 15, 2014, 7:10 AM UTC

monkey26 wrote: post #76

Ayey_ wrote: post #71

Earlier quoted context omitted.

Would you mind sharing that work-flow? I'm interested in how this is done, since i have failed to do it on several occasions.

I have failed to adopt it as well, and am still using Vagrant, but as my desktop is Linux, vagrant is a little bit of overkill. The primary stopper for me is run vs start I think - and persistence of the most recent change I made in an environment.

`run` creates a container from an image and tries to start it. If it doesn't start you have a stopped container in `docker ps -a`. If it does start, you have a started container in `docker ps`. You could stop a started container if you wanted, and later start it again without having to use `run` all over again.

Sometimes running fails to start the container because there's a problem. You'll then have a stopped container.

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

#83

Post by projectramo » Fri, Aug 15, 2014, 3:48 PM UTC

rabino wrote: post #57

projectramo wrote: post #45

Earlier quoted context omitted.

We should not be too harsh with people who inadvertently post their secret key. They may be very nice, well-meaning, smart people who, you know, make a mistake and post their key. Maybe it is in an environment file, and they post it to their public github. Could happen. Maybe they forgot and went to sleep, and found out their key got jacked. Maybe -- hypothetical here -- someone ran up $1000s of dollars producing bit…

Not sure you are talking to me, but my comment wasn't harsh at all. Just trying to make sure he noticed and fixed it in case it was his real key.

No, I was talking about a "friend" of mine who got himself in trouble.

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

#84

Post by victorlin » Thu, Aug 21, 2014, 1:39 AM UTC

ninkendo wrote: post #60

After having used docker for "real" things for the past 8 months or so, I definitely agree with you that it kinda sucks. Docker's strengths come from the workflow you get to use when you use it... "Run /bin/bash in ubuntu" and it just works. For developers that's great. For a backend that does the heavy lifting for you when you're developing a lot of operations automation (like a PaaS), it starts to break down. Just…

Yeah, docker is god damn slow. The layer file system is a great idea, but its implementation sucks. When you push an image which its base image is already pushed, you will see tons of

Image already pushed, skipping Image already pushed, skipping Image already pushed, skipping ...

This is really stupid, it just cannot compare the list of layer image and push or pull the missing parts. And the pushing and pulling operations are slow like hell. It's really painful to use it in production. It slows down your whole deployment process, and it eventually becomes the bottleneck. It's really funny they pick go language which advertises for performance, but they failed to make very basic task works efficiently.

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

#85

Post by cpuguy83 » Fri, Aug 22, 2014, 7:30 PM UTC

And /etc/hosts, /etc/resolv.conf are now writable.

docker run -d regisry

`docker rmi` can be tricky, but it can and does actually remove an image. The problem is if there is an image with multiple tags at the same commit (layer)... in this case it just untags until there are no other tags pointing to that commit. Alternatively, you can use the ID, I believe that always removes as expected.