Aus dem Leben eines Windows Docker Toolbox Nutzers:

Mein Setup: Windows 7 + Docker Toolbox v1.12.6 (Docker Host via VirtualBox)
Mein Problem: docker-compose up XYZ wirft seit dem Update der Docker Toolbox einen Fehler:
$ docker-compose.exe up XYZ
Creating dockerhost_XYZ_1
ERROR: for XYZ Cannot create container for service XYZ: create \mnt\volumes\Storage: "\\mnt\\volumes\\Storage" includes invalid characters
a-zA-Z0-9][a-zA-Z0-9_.-]" are allowed
ERROR: Encountered errors while bringing up the project.

Meine Beobachtung: Ein Problem mit dem Volume des Service XYZ (via docker-compose.yml definiert). Neben anderen Änderungen und der Erfahrung aus connection reset by peer… damn you peer liegt es bestimmt am zuletzt ausgeführten Update. Diesmal die Docker Toolbox.

Die Lösung: Nach einer Online-Recherche wurde ich tatsächlich fündig. Ein Bug in Docker Compose Can’t mount a volume on Windows 7 #607.

Mein präferierter Workaround (solange die neue Toolbox nicht released ist):
Folgender Eintrag in meiner .bash_profile
export COMPOSE_CONVERT_WINDOWS_PATHS=1

Lessons learned: Ich sollte zukünftig vor einem Update die Known Issues auf GitHub durchlesen.

Aus dem Leben eines Windows Docker Toolbox Nutzers:

Mein Setup: Windows 7 + Docker Toolbox + Docker Host via VirtualBox + neu eingerichtet eine Custom Docker Registry im LAN
Mein Problem: docker pull eines Docker Image von der Registry endet im „… connection reset by peer“
Meine Beobachtung: Mal geht’s teilweise, mal geht’s gar nicht.

Die Lösung: Nach der Lektüre dieses Threads habe ich ein Update auf VirtualBox-5.1.10 ausgeführt. Tadaaaa, klappt endlich.

Last week I got the chance to meet Bruno Souza, Edson Yanaga and Otávio Santana on their Java Euro Tour through Germany, Switzerland and Spain supported by Jelastic and dogado.

While writing this post the Java Euro Tour is over already, but it is never too late to say: Thank you for your visit!

• Thank you Bruno for visiting and sharing your view of beeing a software craftsman. I never had such a delightful and passionate presentation about our profession before. It really felt good to listen to you and to be reminded why you, me and all the others out there love to compete with ourselvers each day. Besides, your talk gave the best overview of all the hyping around (Docker) containers and DevOPs I had until now. *thumbsUp*
• Thank you Edson for sharing your journey from Monoliths to Microservices. I’m really excited and I look forward to all my upcoming journeys following your route: Start in legacy code town, passing by the golden circle and, eventually, plant some microservice seeds, some kind of Stranglers, at the end of each trip. In the mean time I browse developers at Red Hat and check out your online journal on such tours.
• Thank you Otávio for making my future Java and contributing to Open Source projects. While I was still puzzling over the upcoming Jigsaw in Java 9, you surprised me with CDI 2.0 in Java SE. And finally, thanks to you, we got some code too :-) It was a pleasure to watch you dive into your code and run it on that sensible piece of hardware. Just you, your compiler and pure java. Wonderful!
  Besides, I’m still struggeling if I shall promote your kind of presentation mode or if I should stick with the netbeans shortcut ;-)
• Thank you Anton Epple for inviting all of us to your place and beeing such a kind host! (And for challenging the presentation mode :-) )

In case you missed them, just have a look at the recorded conversations with Java Champions and JUG Leaders along the way and, next time, make sure not to miss them again!