11 ms·
Docker 1.0
- davidcelis 12y agoUnfortunately, installing the Docker client is currently broken, at least via brew: https://github.com/dotcloud/docker/issues/6256 https://github.com/dotcloud/docker/issues/6256 — This made it into 1.0 The CHANGELOG states Production support as the 1.0 feature, but how am I supposed to be confident using Docker 1.0 in production if I can't use the client from my own machine? Or is there some other preferred install method?
- RKearney 12y agoThe very first thing I clicked on was "Try It!"[0] in the header. I was then promptly greeted with a 404 error. I'm with you on this one. Not exactly confident about using this in a production environment quite yet. [0]https://www.docker.com/resources/tutorial/ https://www.docker.com/resources/tutorial/
- sergiotapia 12y agoYou need to use docker pull learn/tutorial - not: docker pull tutorial
- ClifReeder 12y agoIn fairness, nobody is using brew to install something on their production environment.
- Goopplesoft 12y agoReally? Never read/worked/etc in a os x server environment, but it seems like brew would be a good package manager for automating installs...
- justincormack 12y agoHardly anyone uses os x server.
- davidcelis 12y agoI do, however, like using the Docker OS X client to interface with my staging and production environments.
- deleted 12y ago[deleted]
- igravious 12y agoAnecdote. Have only very recently tried to install Discourse via Docker on Centos 6.5 (the only recommended way to install Discourse now) and it failed. edit: yes I realise that the docs tell you to use a 64-bit version of a recent Ubuntu
- slight 12y agoThe Discourse Docker image doesn't seem to be very well maintained. I tried it and it ran for ages before failing. Don't judge docker by it. I couldn't get it to work but I'm using Docker to handle my XMPP server (as a test of the tools) and quite happy with it.
- mordocai 12y agoThis https://docs.docker.com/installation/mac/ https://docs.docker.com/installation/mac/ says to use a download and doesn't mention homebrew. If it doesn't work then I understand not feeling confident in their release, so you should try it! TLDR: Homebrew does not appear to be an official install method.
- davidcelis 12y agoThanks a bunch for that link; I wasn't aware that they had also released a very handy .pkg installer for boot2docker + docker. The installer works perfectly and, since it's the officially supported installer method, I'm polling to get the docker and boot2docker formulae removed from Homebrew to ease confusion: https://github.com/Homebrew/homebrew/pull/30013 https://github.com/Homebrew/homebrew/pull/30013
- shykes 12y agoHomebrew is not an officially supported target. We build an official Darwin client as part of every release, on a Linux server using go cross-compile. Build failure of that target (or any target) would atomically roll back the entire release. You can check out our build and release tooling in the ./hack subdirectory. Fwiw I use the Darwin build every day and it works great.
- turnip1979 12y agoAnyone know if there is a livestream or videos available from Dockercon?
- kylemathews 12y agoNo livestream but they'll be posting videos after the conference.
- 1qaz2wsx3edc 12y agoCongrats on the 1.0 Docker!
- bhhaskin 12y agoI haven't given docker a try yet, but I think I might have to give it a go.
- _eqet 12y agoGreat work!
- muloka 12y agoCongrats to the Docker team on 1.0! Every time I use Docker it leaves a grin on my face.
- nickstinemates 12y agoThank YOU. Users are amazing. Use more. Keep it up!
- CSDude 12y agoAt last, it was already production ready, mostly bug free and fast enough, but having 1.0 release makes one more comfortable when they highly depend on it.
- odonnellryan 12y agoSee here: https://github.com/dotcloud/docker/blob/v1.0.0/CHANGELOG.md https://github.com/dotcloud/docker/blob/v1.0.0/CHANGELOG.md Not sure what "Production support" really means. But, Docker is awesome software!
- derefr 12y agoQuote from the blog post: > First, while many organizations have cheerfully ignored our “Do not run in production!” warnings, others have been waiting for a level of product maturity before deploying production workloads. This release’s “1.0” label signifies a level of quality, feature completeness, backward compatibility and API stability to meet enterprise IT standards. In addition, to provide a full solution for using Docker in production we’re also delivering complete documentation, training programs, professional services, and enterprise support.
- soccerdave 12y agoVersion was changed to 1.0.0-dev in Github. I think this was accidental that the version said 1.0.0.
- opendais 12y agoDocker .11 was also Docker RC 1 for 1.0, .12 was RC 2. So I think it may not be accidental.
- soccerdave 12y agoYep, I was wrong, http://blog.docker.com/2014/06/its-here-docker-1-0/ http://blog.docker.com/2014/06/its-here-docker-1-0/ I was just a little skeptical since there wasn't an official blog post to go with it
- jacquesm 12y agoFor those wondering what docker is: http://www.docker.com/whatisdocker/ http://www.docker.com/whatisdocker/
- Jgrubb 12y agoOn that, I was at DrupalCon last week and the most mind expanding session I went to all week was about container-ization in general. I'm a front end dev, but I'm really interested in knowing more about Docker. Here's the video -- https://austin2014.drupal.org/session/mo-servers-mo-problems https://austin2014.drupal.org/session/mo-servers-mo-problems
- csixty4 12y agoAnd here's "narrated slides" from my WordCamp Philly talk on containerization, Docker, and Dokku this past Saturday. The video isn't ready yet, and my talk was interrupted by a pride parade and some technical difficulties, so this is probably the best way to experience it. https://www.youtube.com/watch?v=ajVHyqeGjV4 https://www.youtube.com/watch?v=ajVHyqeGjV4
- dpcan 12y agoIs there a very specific use case someone could share so I can visualize what docker really is? Something more than a hello world.
- jacquesm 12y agoLet me try: Say you're going to deploy an open source application that requires a whole pile of dependencies. Normally you would have two choices: ship the source with a bunch of readme's and let the recipient figure out how to install your software and all dependencies and to resolve any conflicts with other software already on the machine (aka version hell). Or you could ship a relatively large fully installed VM image of the OS+all the application parts and dependencies (this may be problematic if your target is a licensed OS). Docker gives you something in between. Think of a chroot'd environment (not that that's what it is, but it shares some concepts) with all the application code, libs and dependencies pre-packaged that should run theoretically out of the box. That way you can have a 'war' like file that contains everything required to run your app and you're 100% sure that it will just work, rather than to have to field a million questions about how to make your app run on 'obscure distro x' or 'obsolete version y'. Another use-case would be that if you're deploying something distributed across a large cluster that you can build your docker container on your desktop box, test it until you're happy and then deploy to your cluster without having to re-test everything. Since the container wasn't changed it should work. It's a way of isolating dependencies between various pieces of software using one single container to hold them all. Of course this approach has its own unique set of problems, but it solves certain things quite elegantly. I hope that explains it and that if it is wrong in some aspect that someone will correct me.
- mmerickel 12y agoI'm glad to see docker stabilizing but it's very disappointing to not see any changes addressing the logging support that was promised in 1.0 (https://news.ycombinator.com/item?id=7712138 https://news.ycombinator.com/item?id=7712138 reply by shykes). The infinitely increasing-in-size and unconfigurable logfiles generated by containers in docker are basically a dealbreaker unless you bake your own logging solution into each container and avoid stdin/stdout.
- jhspaybar 12y agoIs a linux tool like logrotate acceptable here? Wouldn't this be able to rotate the std-out infinitely increasing log files? Yes this isn't built in to docker, but does seem like a reasonable solution.
- mmerickel 12y agoI've never seen a recipe documenting whether docker can handle a logrotate. Most daemons require you to HUP them after rotation. In general logrotate is a complete hack in the way it interacts with daemons.
- jacquesm 12y agoHow is this different from using a regular non-docker setup?
- mmerickel 12y agoThere are docker commands (docker logs) that are dependent on this format. The primary issue is that if you deal with logs yourself via attaching to the container and piping them somewhere, the logs are still duplicated to these json files. It's unexpected, a waste of space and insecure. That being said, logrotate would sort of work with caveats since the json files are one entry per line last I checked.
- derefr 12y agoI wonder if a very simple solution would be enough: with a one-line change, the logs could be created as named pipes instead of files. Then you could just write some upstart scripts/systemd units that do cat /run/docker/mypipe >/dev/log And you'd be good. --- I'm not sure this is the right approach, though. In my opinion, docker shouldn't log at all—containers are unix processes, and Unix processes log to ephemeral stream-sink endpoints (think AWS SNS topics) called stdout and stderr. To collect and persist those logs, the Unix Way is to use shell redirection to "attach" those endpoints to subscribers. Now, in Docker's daemonized run mode, these pipes are just hanging loose. But docker provides the "docker attach" command precisely so you can reattach them to something (or as many somethings) as you like. All you have to do if to get sensible logging if you're using e.g. Upstart is to create a service that runs "docker attach <mycontainer>": the logs will flow from the container's stdout/stderr to the service's stdout/stderr, and Upstart will catch them and handle them sensibly from there. So, having done something like that, the important bit would actually be making sure docker doesn't do its own broken logging at all, except in the case of test containers that will never be attached to. Actually, this also cuts across the use (or lack thereof) of the --rm flag: it'd make sense for containers started with --rm to not log. (The generalization of the --rm semantics would seem to put such containers in the same category as e.g. EC2 instance-store instances.)
- mmcclure 12y agoThis is awesome! Now CoreOS just needs to follow suit and hit 1.0...
- tonyhb 12y agoIn their last article they said they're about a week behind, so by next week we should be production ready on all fronts. Cannot wait.
- Dorian-Marie 12y agoHere is the CHANGELOG: https://github.com/dotcloud/docker/blob/master/CHANGELOG.md https://github.com/dotcloud/docker/blob/master/CHANGELOG.md 1.0.0 (2014-06-09) Notable features since 0.12.0 * Production support
- marklit 12y agoYou'd think IPv4 connectivity with containers would be high up the priority list to get working: https://github.com/dotcloud/docker/issues/2174 https://github.com/dotcloud/docker/issues/2174
- jacquesm 12y agoIt looks like it is pretty high on the priority list, the last update in that thread is on Friday.
- rmanocha 12y agoDo we know yet if mounting a directory from host as a data volume is available in Mac OS X now? I think something along these lines was promised (not able to find the source now) - it's the only thing blocking me from using docker as my everyday dev environment.
- bacongobbler 12y agoStill a work in progress. See https://github.com/dotcloud/docker/issues/4023 https://github.com/dotcloud/docker/issues/4023
- shykes 12y agoThis is a huge undertaking and we are determined to get it right. Thanks again to Brad Fitzpatrick and everyone else contributing this building block!
- evancordell 12y agoI've been working on getting a dev environment set up with docker over the weekend, and I finally have something I'm happy with. I don't have a nice blog post to show you, but the basic idea is: - Use the CoreOS Vagrantfile (+ extra files like user_data and any service unit files) - Share your local directory with the vagrant box with config.vm.synced_folder (just uncomment a line in the Vagrantfile) - set the DOCKER_HOST and FLEETCTL_TUNNEL env variables so that the local tools work transparently with the vagrant box. - Then you have the option of running a docker image with -v and sharing the vagrant directory with the docker container, or - You can dive into CoreOS stuff and write a unit file for your service, and that will share the directory with -v Now local files sync into the docker container, and if the server is configured to reload on file changes you're good to go.
- rmanocha 12y agoThanks a lot, I'll give this a shot tonight. Not too familiar with CoreOS yet; I was hoping that I'd simply be able to mount a volume similar to how I might do it in Linux. I understand the problems with doing that though...
- MoOmer 12y agoCongrats to the team - I'm wrapping up a deployment on 0.11 now; and, though there are definitely some pain points, docker wasn't even near the most painful part of the process.
- lavalla0 12y agoIs the devicemapper storage driver ready to use in production?
- heyimwill 12y agoWhy wouldn't it be?
- nknighthb 12y agoWhen I was working on a docker-based build/test/deploy solution a few months ago, its performance was so anemic I wanted to tear (what's left of) my hair out, especially during a development/testing cycle. I got sidetracked by other things and haven't gotten back to it, but if I do and it's still as bad as it was, I don't think I'll want to continue on that path.
- contingencies 12y agoI haven't seen the code but have played with LVM2 LVs / device mapper myself on my own containers-based infrastructure and also seen performance issues in some situations. Fundamentally (1) LVM2 LVs are capable of single-depth snapshots only, forcing hacks like an actual full blockstore copy if code expects duplication. (2) Docker was written primarily against aufs which provides rapid arbitrary-depth snapshots. I suspect this is the heart of the issue... ie. Docker expects features this storage subsystem wasn't designed to support.
- philbarr 12y agoI am right in thinking that Docker can virtualize any environment, as long as that environment is Linux, right? Because I have an office plugin I need to test against various different version of office and content management repository and so on and it feels like this would be ideal. Possibly I'm reaching here - but I thought I'd ask anyway, I don't know much about Docker.
- nickstinemates 12y agoThe Microsoft Azure team is talking at DockeCon tomorrow. It's just the tip of the iceberg in terms of our collaboration together. More to come. I'm extremely optimistic.
- bentcorner 12y agoI don't have any experience with Docker either, but from the little I've read it's built on top of Linux Containers (http://en.wikipedia.org/wiki/Linux_Containers http://en.wikipedia.org/wiki/Linux_Containers). Windows has App-V (http://en.wikipedia.org/wiki/Microsoft_Application_Virtualization http://en.wikipedia.org/wiki/Microsoft_Application_Virtualiz...) which seems like a similar technology (I believe Office 365 uses this). Note that Office plug-ins are specifically called out as something that is problematic with this tech.
- euske 12y agoThere's no single mention of Linux in http://www.docker.com/whatisdocker/ http://www.docker.com/whatisdocker/ page. Yet it looks like it's currently (almost) Linux-only framework and it's highly dependent on the OS specific feature. Comparison with VMs seems a bit unfair to me, because it would sound that Docker can emulate any architecture too. They even said ``"Dockerized” apps are completely portable and can run anywhere - colleagues’ OS X and Windows laptops.'' which adds confusion, because it sounds like it's a cross platform format, which apparently isn't. I don't deny this is immensely useful software for people using the clouds, but the way it's advertising is a bit misleading to me.
- tachion 12y agoSadly there is no new things to support FreeBSD Jails, a competitive (and much more matured) container technology than Docker's default LXC (despite earliers mentions of plans for supporting FreeBSD in version 1.0)...
- nickstinemates 12y agoSome of the core abstractions are there. Get started. We'll follow :)
- yebyen 12y agoI think that what you're asking for (a Jails execution driver) is really _not_ so far out of bounds, mostly given that FreeBSD has really good support for binary compatibility and Linux emulation, so FreeBSD is actually the _one_ good platform to try this with (one of the best candidate platforms?) but one thing, that people all keep repeating this about LXC makes me grumpy... The LXC driver is _not_ the default anymore as of ~0.9, Docker switched to pluggable execution and storage drivers at that time and shortly after, started using the new "native" driver for execution (which does not use LXC at all, but uses the underlying kernel services directly, like namespacing and cgroups, that are also used by LXC). The execution driver LXC provides the same experience from before the pluggable driver model happened, and it's still available but not the default anymore. Am I being pedantic, is my information wrong, or has this just not been heavily publicized before (maybe it's actually a very small distinction and I should stop repeating it?)
- justincormack 12y agoI don't think the binary compatibility and Linux emulation will be anything useful - there is no emulation of containers, and no one would want to run a Linux process in their container. But yes, some framework is there.
- yebyen 12y agoI think the point would be not to use linux containers or any abstraction around the parts that fuel LXC, but to use BSD Jails on the idea that they are "battle tested" Just as you might not trust Docker's native driver more than LXC, if you most cynically regarded LXC as an "example of a failed marketing experiment" and then Docker as "the first notable consumer of cgroups and linux kernel namespacing, and certainly too new yet to trust with anything important" -- but there are plenty of high-profile consumers of the FreeBSD jails and it is trusted by many to keep processes separate. I mentioned emulation and binary compatibility, maybe because it's the thing that's missing in many other cases that wind up being responsible for alternative platform support getting back-burnered and second-classed in Docker community. Where there might be lots of people who want to use Docker on i386, it's not supported probably most of all because it would lead to a bad user experience and fragmentation. Binary images are all built for amd64 linux at this point. I bypassed the warnings, I use it, I'm not bothered that I have to rebuild for my specific architecture. The docker users at large can still use my images, and maybe I'm a bad citizen for pushing images compiled this way, but it works. Similarly there are probably a lot of people testing Docker on ARM, but they can't use any of the pre-built containers that are provided by the majority docker community, tested and supported. Their architecture is even farther out from being supported. They have the drawback that they can neither receive blood from "O" nor give to "AB" if you'll indulge the analogy of images to blood types, they have one of those weird blood types that doesn't even register in the statistics with a reasonably sized sample. Anemic, maybe. If you had a jails execution driver, you certainly don't have to use Linux processes or binary emulation, you can build your containers with a BSD base and BSD toolchain. The point is that in theory, you probably could skip that step and get working with existing binary images built from Linux distributions. It would quickly be a better "alternative platform" than any of the other existing contenders (different architectures) who you could already see in the docker ecosystem at this point; it could probably run many existing container images out of the box, on a FreeBSD host with amd64 architecture. The contained software really shouldn't care what execution driver keeps it isolated, at least in theory. In practice someone with more knowledge than me can probably say what a bad idea this is, maybe because either "congrats, you just invented Virtualization" or "wrong, jails won't keep those processes separated."
- general_failure 12y agoCongrats! I would love to see user namespace support.
- nickstinemates 12y ago"It's complicated" - crosbymichael, my favorite maintainer of all time. Rest assured we're working on it and it's a priority.
- shykes 12y agoYes, user namespaces are coming soon.
- sysexit 12y agoA release that seems somewhat rushed, and a Red Hat media event tomorrow. I wonder if the two are related.
- ritchiea 12y agoToday is the first day of docker con [1], that is surely the reason for the announcement. 1. http://www.dockercon.com/ http://www.dockercon.com/
- dang 12y agoUrl changed from https://github.com/dotcloud/docker/releases/tag/v1.0.0 https://github.com/dotcloud/docker/releases/tag/v1.0.0, since there were two threads on the front page and this one has the more extensive discussion.
- mattjaynes 12y agoDocker is an amazing tool, but there are quite a few misconceptions about it. Nearly all the articles and examples seem super easy, but it's quite a challenge to use in an actual multi-host production environment supporting mission-critical systems. This can send the wrong message to beginners and send newbies down the wrong path, which ends up as a disservice to Docker when they hit the complexities and become disillusioned with it. To address those misconceptions, I've just posted the article "Docker Misconceptions": https://devopsu.com/blog/docker-misconceptions/ https://devopsu.com/blog/docker-misconceptions/ I spent about a month working on setting up Docker for production scenarios and reading everything I could on it (all the docs, courses, and well over 100 articles - see Docker Weekly for a wealth of resources). My post covers the main misconceptions I see popping up and also some advice for simplifying Docker use if you do decide to use it for multi-host production. I'm sure I've probably missed some things, so please chime in if I've missed something important.
- kiyoto 12y agoThanks for a great summary. >For logs, you can either use a shared directory with the host or use a remote log collection service like logstash or papertrail. I would not put Logstash (software) and Papertrail (SaaS) in the same bucket though. With Logstash (or any other data collectors like Flume, Fluentd, etc.) you need a backend system to go with it. Sorry to nitpick, but logging is something I work on/think about all day, so I thought to point it out.
- wpietri 12y agoThanks, that's exactly the sort of thing I was hoping to learn from the HN comments. In the post you link above, it seems like you're mainly comparing Docker to traditional, non-virtualized setups. Do you (or does anybody) have thoughts on comparing it to virtualized environments? I recently experimented with Xen as a way to isolate services, and it seemed awfully heavy; does Docker end up being a lighter burden?
- lojack 12y agoIt's lighter in the sense that it should require less resources to keep each container running, but comparable in the sense that you still need to orchestrate how services connect and how each container is configured.
- curiousDog 12y agoLooks very promising. Too bad their jobs page says they only want engineers with Go experience. Why does language matter?
- tomerbd 12y agoWhat is the difference between this and rpm+puppet with rpm+puppet I have no problems installing my apps with my dependencies to any server and best of all as its the developers who create the rpms+puppets they hand it as a building block to production who install it in a few seconds on any machine.
- jradd 12y agoJoin #docker on IRC for anybody struggling with Docker. Everybody is very helpful on there. And I have learned a lot just by supporting others, and asking questions myself.
- FooBarWidget 12y agoI was hoping that Docker 1.0 would have a 'docker login' or 'docker shell' command for spawning a shell within the container. In baseimage-docker (https://github.com/phusion/baseimage-docker https://github.com/phusion/baseimage-docker), we run an SSH daemon so that people can login to the container for administrative purposes. In the past, it that approach was criticized because it was also possible to use lxc-attach, but since Docker 0.8 or 0.9 lxc-attach is not usable anymore because the default Docker backend no longer uses LXC. The Docker authors promised they would have a solution in the future, but sadly it didn't make it to 1.0. I guess we'll continue to use SSH until they have an official solution.
- heavenlyhash 12y agohttps://github.com/polydawn/siphon-cli https://github.com/polydawn/siphon-cli might address your needs for now. It's just a tiny little wrapper around terminals that shuttles the connection over a unix socket... which in the case of docker, you can put on a mount to access from the host. Author here; I built it to replace that use case of sshd with something that doesn't have the overhead of key management. Of course if you're doing something with network gaps involve, sshd might still be the right answer for you.
- MoOmer 12y agoI still use this on 0.11: docker ps -l --no-trunc lxc-attach -n xxxxxxxxxx
- mixmastamyk 12y agoDocker has a lot of potential and I recently really dug into it. Seems like there are still some rough edges though. For example, when working you end up with a lot of old items or layers hanging around, and its not clear how to remove or collapse them. I've seen posts complaining about this. Also, on some commands it outputs the the id as the first column, and sometimes the fourth, or other column. This will make script pipelines harder to write. I've not gotten far enough to worry about logs, but I hear there is an issue with them. It is very true I may not be using it correctly... or there could have been lots of stuff still to be done for a .12 release?
- brianxq3 12y agoI think most (all?) of the commands can be performed over the API with JSON coming back, so the order of output shouldn't matter too much.
- sergiosgc 12y agoJSON over HTTP is not an alternative to a good CLI interface. As such, your comment, although true and happily so, is a non-sequitur.
- ilaksh 12y agoIs there a way to add a Docker Webhook programmatically?
- paulannesley 12y agoNote that Docker 1.0 (and the brief 0.12.0) changed its TCP port from 4243 to 2375. If you use a remote client (like `brew install docker`) and have `DOCKER_HOST=4243` in your environment, you'll have to update it. To ease this pain across a large team, I'm considering using netfilter/iptables or a TCP proxy to make the old port available in our VM environment during transition. https://github.com/dotcloud/docker/commit/5febba93babcf8c4b01862e88b6f6e11a1532bc8 https://github.com/dotcloud/docker/commit/5febba93babcf8c4b0...
- x_soda 12y agoCan someone explain to me the practical differences between vagrant and Docker? I know they're implemented in quite different ways, but in my utterly non-devops mind they seem to achieve the same thing. Wrong?
- billmalarky 12y agoScroll down to the bottom of this page to see Docker VS VM's. https://www.docker.com/whatisdocker/ https://www.docker.com/whatisdocker/
- kolev 12y agoGreat news! I just wonder why Docker is getting so much attention and Google's lmctfy doesn't get any?
- wmf 12y agoIMO the goodness of Docker is the build system, images, layers, and the index. lmctfy has none of those features.
- shykes 12y agoDocker and lmctfy have largely joined forces - Rohit and Victor are now core maintainers of Docker and kicking ass contributing all sorts of low-level system awesomeness :) https://github.com/dotcloud/docker/blob/f4b60a385cbaae045674146644294e9c55129b3f/pkg/libcontainer/MAINTAINERS https://github.com/dotcloud/docker/blob/f4b60a385cbaae045674...
- kolev 12y agoThat explains it, thanks!
- jtchang 12y agoGripe: When you start a container and forget to forward a port into it you can't do it at a later time. This is braindead.