Software-update: Docker 0.7

Docker is een opensource tool voor ontwikkelaars, waarmee installatiepakketten kunnen worden gemaakt. Het stopt de applicatie inclusief alle onderdelen waar het afhankelijk van is in een virtuele container, die op nagenoeg elk willekeurige Linux-machine kan draaien. Deze week is versie 0.7 van Docker beschikbaar gekomen. Uitgebreide release notes kunnen hier worden gevonden, dit zijn in het kort de belangrijkste verbeteringen:

Docker 0.7 runs on all Linux distributions – and 6 other major features

So, Docker 0.7 is finally here! We hope you’ll like it. On top of countless bug fixes and small usability improvements, it introduces 7 major features since 0.6.0:

• Feature 1: Standard Linux support
• Feature 2: Storage drivers
• Feature 3: Offline transfer
• Feature 4: Links
• Feature 5: Container naming
• Feature 6: Advanced port redirects
• Feature 7: Quality

You can see the full Changelog on the repository.

Versienummer	0.7
Releasestatus	Final
Besturingssystemen	Linux
Website	Docker
Download	https://www.docker.io/gettingstarted/#h_installation
Licentietype	Voorwaarden (GNU/BSD/etc.)

Reacties (7)

[Kalief]

Major feature 7: Quality

[TheNephilim]

Obviously, “quality” isn’t really a feature you can add. But it’s become important enough to us that we wanted to list it. Quality has been a big focus in 0.7, and that focus will only increase in future versions. It’s not easy keeping up with a project as incredibly active as Docker – especially when its success came so quickly. When the floodgates opened, much of the code was still immature, unfinished or scheduled to be refactored or rewritten. 6 months and 2,844 pull requests later, much of it is still there, drowned in a daily deluge of contributions and feature requests.

It took us a while to find our bearings and adapt to the new, crazy pace of Docker’s development. But we are finally figuring it out. Starting with 0.7, we are placing Quality in all its forms – user interface, test coverage, robustness, ease of deployment, documentation, consistency of APIs – at the center our development process. Of course, there is no silver bullet: Docker still has plenty of bugs and rough edges, and the progress will be slow and steady rather than the elusive “grand rewrite” we initially hoped for. But day after day, commit after commit, we will continue to make gradual improvements.

Te lezen bij de release notes, waar ze punt voor punt uitleggen wat er onder verstaan wordt.

[intrixius]

Dit is echt een super systeem; in plaats van met bloated VMs te werken, kan je voor elke service apart een minimale container opzetten, die met elkaar kunnen communiceren via links (zie hier ), maar wel van elkaar geisoleerd zijn...

Ik ben (als developer/system administrator) al een paar weken aan het experimenteren met Docker, maar wat ik me af vraag is of dit systeem ook bedoeld is om (eens docker "volwassen" genoeg is) gebruikt te worden om een "productie" webserver e.d. (apache-container, mysql-container,...) te draaien. Want als ik het goed heb worden alle veranderingen (zoals bijvoorbeeld uploads) niet automatisch terug opgeladen als je de container herstart...
Heeft iemand daar een klare kijk op? Moet je datafiles (zoals DB-files, log-files,...) buiten de container opslaan, of zijn er andere manieren?

[Reactie gewijzigd door intrixius op 24 juli 2024 07:53]

[Stephan Oudmaijer]

Jep, buiten de container, tenzij het temporary files zijn en dan nog moet je oppassen dat je dan niet je container opblaast met je tmp files (log, uploads etc). Typisch mount je een FS waar je persistent data op zet. Of gebruik je externe services ((no)sql, etc).

Wat trouwens wel nice is. Als je niet alleen met Docker je ding kunt doen, dan kun je ook Docker in OpenStack hangen. Dan heb je best of both worlds. Full blown VM`s, Docker en LXC.

https://wiki.openstack.org/wiki/Docker

[Reactie gewijzigd door Stephan Oudmaijer op 24 juli 2024 07:53]

[Verwijderd]

There are multiple ways to inject data into containers of share existing files between containers.

• mounting a folder with data into a new container when it is started, for example for large data files, DB files of configurations folders.
  We have an example of Jenkins server running inside a container and using JENKINS_HOME from external folder which is committed to git.
  Or another example of development project where source are located on the host machine and can be edited with your normal IDE and mounted into container for running builds and tests
• adding files to the image during the build time. This is good for files which does not change frequently but you can also use it during the build of your application and as a final result deliver a docker image instead of war file or RPM or anything like that.
• copy files into container while it is running. You can also snapshot containers once you added new files to them and start new containers based on those snapshots. For example you can run each test suite in a separate container and store the snapshot as a part of test results. This way developers will be ably to reproduce environments quickly and easily.
• Configure your container during the startup using CMD. For example you need to start a cluster of 10 containers but configure different hostnames for each one. Or configure different DB access point for testing and production environments. Such configurations are simple and quick therefore are reasonable for startup time.
• Share data through network by exposing containers ports thought the host machine or by configuring full networking with IP, ssh or whatever is appropriate. In this situation, containers will act similar to full VMs.
• new links mechanist introduced in version 0.7 which allows you to link containers running in parallel and explore resources of each other. Using this mechanism you can configure multi container setups and replace parts of the setup with fake containers for testing for example.

I'm pretty sure I forgot something and I didn't even start talking about using orchestration layer like Ansible or Heat in OpenStack or new tools like Shipyard, Serf, etc.

We are arranging a meetup for Docker container introduction which will be today at 7PM http://www.meetup.com/Docker-Amsterdam/events/151033782/
and we are going to continue talking about Docker at similar events which we will schedule regularly.
You're all welcome to join.

[Reactie gewijzigd door Verwijderd op 24 juli 2024 07:53]

[sfranken]

Docker werkt inderdaad wel handig, vooral in combinatie met CoreOS waar het standaard inzit (CoreOS is weer op basis van Chromium OS en moet de infrastructuur a la Google nabootsen)

[webdevotion]

https://github.com/progrium/dokku is ook erg prettig
om je eigen PaaS mee op te bouwen. Gebruikt Docker op de achtergrond.