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

Docker Jumpstart

github.com

Post reply on HN
Print view View original

31–40 of 45 posts

Re: Docker Jumpstart

#31

Post by laex »

zenlikethat wrote: post #30
laex wrote: post #13

Earlier quoted context omitted.

For some reason, when using docker machine on a mac, the VM always fails to start and freezes at the "VM starting" phase. For this reason, I've had to switch back to boot2docker.

Super sorry to hear - we've had some issues with VirtualBox around networking and some setups we didn't anticipate -- Would be really appreciative if you'd give the latest 0.3.0 release candidate a whirl and see if it fixes the issue for you: https://github.com/docker/machine/releases .

Yes, It looks like it has been fixed. I tried creating multiple VMS ( dev, staging ) a few times, and It worked properly. Thanks.

Edit: I tried v0.3.0-rc2

Re: Docker Jumpstart

#33

Post by icebraining »

eli wrote: post #6
weaksauce wrote: post #2

The short introduction on that tutorial is much better than that actual docker site and 10-15 min interactive tutorial on what docker actually is and what it can be used for. A note to other developers, it's a good idea to not use some language without first defining the word... Especially if it's an overloaded term.

Agreed, it's a nice intro. I still think the hardest part is understanding how docker fits into the bigger picture. I think I've more or less figured it out on my own, but I struggled with e.g. do I want my source built in the image or mounted as a volume?

If you're loading the source from outside, aren't you losing the advantages of immutability of the Docker container? Suddenly the same image may have different behaviours depending on the state of the code outside.

Re: Docker Jumpstart

#34

Post by icebraining »

nisa wrote: post #22
pibefision wrote: post #20

Is docker ready for production? Is someone using it on real production environments? Most recipes at Docker Registy are a mess, and with plenty of bugs

I guess it depends on what you want to do.. I stopped caring and looking at docker after reading this: http://iops.io/blog/docker-hype/ Using btrfs as cow is not ready for production (yet and likely not in the near future) - believing otherwise made the last few feeks quite miserable.

Using btrfs as cow is not ready for production

Yes, but it's not like they don't warn people. From the Docker docs:

"This backend is pretty fast, however btrfs is still maturing and is not considered production ready for heavy write loads. Mounting /var/lib/docker on a different filesystem than the rest of your system is recommended in order to limit the impact of filesystem corruption. You would also want to mount the volume directory /var/lib/docker/vfs/ on a standard XFS or EXT4 filesystem to ensure container data is protected."

Re: Docker Jumpstart

#35

Post by xchaotic »

icebraining wrote: post #33
eli wrote: post #6

Earlier quoted context omitted.

Agreed, it's a nice intro. I still think the hardest part is understanding how docker fits into the bigger picture. I think I've more or less figured it out on my own, but I struggled with e.g. do I want my source built in the image or mounted as a volume?

If you're loading the source from outside, aren't you losing the advantages of immutability of the Docker container? Suddenly the same image may have different behaviours depending on the state of the code outside.

That's why you want to use volumes for mutable data such as your source code repo - you isolate the changing parts and keep the containers static.

Re: Docker Jumpstart

#36

Post by UserRights »

When you start playing around with docker and come to the area where you start to see that many things that should be very easy start to be really complicated, then you should take a look at lxc and the upcoming lxd and compare.

Re: Docker Jumpstart

#37

Post by icebraining »

xchaotic wrote: post #35
icebraining wrote: post #33

Earlier quoted context omitted.

If you're loading the source from outside, aren't you losing the advantages of immutability of the Docker container? Suddenly the same image may have different behaviours depending on the state of the code outside.

That's why you want to use volumes for mutable data such as your source code repo - you isolate the changing parts and keep the containers static.

But if the source is mutable data, what isn't? Everything eventually mutates - dependencies have updates, configurations change, etc. Isn't the point of images that you "freeze" a static release that can be deployed everywhere?

It seems that by that point you've lost the advantage of using images; if parts of the system must be loaded outside of the container, it seems you might as well simply use a configuration manager to install the stuff and then run LXC/LXD containers instead of using images at all.

Re: Docker Jumpstart

#39

Post by kimi »

pibefision wrote: post #20

Is docker ready for production? Is someone using it on real production environments? Most recipes at Docker Registy are a mess, and with plenty of bugs

We have been running hundreds of instances for the last couple of years, and so far, no big issues.

Re: Docker Jumpstart

#40

Post by brunoqc »

laex wrote: post #25

Anybody wanting to try out Docker + GoLang + AWS Beanstalk, I've made a sample app / guide here - https://github.com/OrganicCoffeeNepal/DockerBeanstalkSample

Thanks for the link.

Is Beanstalk worth it? Is it cheaper than an ec2 instance?

Post reply on HN