Announcing Docker 1.1.0

http://blog.docker.com/2014/07/announcing-docker-1-1/

by bpierre • 12 years ago

98 28 12 years ago

blog.docker.com

grakic• 12 years ago

Using tar file as context for docker build we can have builder containers building images for new containers: docker run builder | docker build -

jaytaylor• 12 years ago

Do they have Mac OSX support yet? How far out is it?

serverholic• 12 years ago

Most likely never. Docker relies on a linux kernel extension which, as you can probably guess, requires linux.

skrebbel2• 12 years ago

I don't understand that. Other kernels may offer features that are similar enough to allow one to implement a large part of Docker on top of it. Nowhere in "docker run -i -t ubuntu /bin/bash" does it say something about LXC.

Example in point: Spoon Studio, a very Windowsy application that does, on Windows, something not at all unlike what LXC does [1]. It allows you to add one layer of filesystem (just one, so no commits) over the host OS's filesystem and then run applications inside there, contained very much like how processes are contained inside Docker containers.

If this is possible right now (and actually these guys were around before dotcloud was even founded), then I don't see why at some point Docker couldn't come available on multiple platforms.

(but I might also completely misunderstand some fundamental thing that makes LXC/Docker completely unlike Spoon and friends)

[1] https://spoon.net/studio

EDIT: downvoters, if i'm a moron, please have the decency to tell me why.

pella• 12 years ago

only OS X Docker client exist.

"The Docker Engine uses Linux-specific kernel features, so to run it on OS X we need to use a lightweight virtual machine (vm).

You use the OS X Docker client to control the virtualized Docker Engine to build, run, and manage Docker containers.

To make this process easier, we've designed a helper application called Boot2Docker that installs the virtual machine and runs the Docker daemon."

https://docs.docker.com/installation/mac/

vectorpush4• 12 years ago

Why would one want OSX support for docker anyway? Does anyone actually deploy OSX in a server environment? This is not a criticism, just a curiosity.

kennu• 12 years ago

Because in the typical Docker workflow, developers (who often use OS X) build container images on their computers.

Anyway, boot2docker works really well nowadays. Even individual port forwarding has been eliminated by using a virtual IP address where all exposed ports are available.

andrewflnr• 12 years ago

Servers aren't the only thing Docker is useful for. I made the plunge to isolate a GUI app and its daemons from my desktop (krita was trying to run KDE daemons on my xfce system, grr). Something like that might be useful. Another possibility is nice development servers, so you can run something in close to the same environment on your work computer as your servers.

magnetikonline2• 12 years ago

It's very handy for development instances of your apps/services too. Often nicer/faster than using Vagrant if that's your bag.

Something I plugged together recently - a W3C HTML5 validator instance in a Docker container: https://github.com/magnetikonline/dockerhtml5validator proving to be really useful vs. my old method of spinning this all up in a VirtualBox instance.

wiml• 12 years ago

In the past OSX has actually been a pretty decent server OS. I wouldn't recommend it for that today, but there are still plenty of reasons someone might want it (legacy systems, developer familiarity with OSX from desktop use, some Apple technologies that are useful even outside a GUI, and so on).

DrJ• 12 years ago

may I interest you in dvm [http://hw-ops.com/blog/2014/01/07/introducing-dvm-docker-in-...]

it's not native, but it makes playing with docker containers from mac osx straight forward.

ninjay• 12 years ago

How is backwards compatibility with Docker? Say I make a container with 1.1.0. Can I still run it on Amazon Elastic Beanstalk (1.0.0)?

shykes2• 12 years ago

Yes, all containers are backwards compatible, pretty much to the first version.

In general backwards compatibility is a big deal in the Docker project - breaking changes are taken very seriously and we try to avoid them as much as humanly possible. That applies to the container image format, Dockerfile format, remote API and command-line interface. It's also important to preserve portability across drivers. For example different storage drivers (aufs, btrfs, devicemapper etc) don't affect the format of the images they produce.

magnetikonline2• 12 years ago

Something I asked @docker on Twitter - where are these newer builds for Ubuntu 14.04/12.04?

https://docs.docker.com/installation/ubuntulinux/

Would love to be able to move to at least the 1.0 stable.

Announcing Docker 1.1.0

Related Stories