[Win10] Updating from 18.06.0-ce to 18.06.1-ce crashes all set of containers

[gpimentelv]

ISSUE TYPE

• Bug Report

OS / ENVIRONMENT

1. Host operating system: Windows 10 1803 Update August 2018
2. Native Docker or Docker Toolbox: Native Docker
3. Docker version: 18.06.1
4. Docker Compose version: 1.22
5. What containers are running: httpd php mysql redis
6. Container versions:

• cytopia/mariadb-10.1:latest
• redis:4.0
• devilbox/nginx-stable:0.22
• devilbox/php-fpm:7.2-work-0.37
• cytopia/bind:0.15

SUMMARY

Just two weeks ago started to get close and personal with Docker, and i came across this magnificent stack called DevilBox.
So, i installed Docker 18.06.0-ce (on Windows 10, too soon to make the jump to GNU/Linux), read the docs, and set my first containers online, it was amazin how easy everything worked on just 10 minutes! no more XAMPP, AMPPS.

Tried some WP/CodeIgniter to warm up, just fine.

The next day, at Windows startup, docker tells me an update 18.06.1-ce is coming, so i did.
After that, everything on docker-compose (For DevilBox) seems to be running normal but failed to connect.

I tried other containers (Nagios) and they worked fine

That's it, 3 days of pondering, nerve-wrecking scenarios to came to th conclusion:

Hey, why don't just rollback to the previous version?

[SOLVED] Just reporting

STEPS TO REPRODUCE

From 18.06.0-ce on Windows 10:

• Cloned the Latest GIT, make the basic changes on .env (Timezone, Intranet Password)
• docker-compose up -d httpd php mysql redis // docker-compose up -d httpd php pgsql redis
• All Fine and Dandy!! MySQL/pgSQL ok, composer ok, laravel/cakephp/ci ok, prestashop/wp/joomla ok
• Stop containers and exit docker

BUT THEN

• Open Docker, update notice shows
• Update Docker to 18.06.1-ce
• Repeat → docker-compose up -d httpd php mysql redis
• Nothing seems to work

EXPECTED BEHAVIOUR

• Same behaviour as 18.06.0-ce

ACTUAL BEHAVIOUR

• Cannot acces Intranet, or connect to MySQL/pgSQL

OTHER INFORMATION

• Dude, im a rookie so no custom moves

[cytopia]

@gpimentelv thanks for reporting this. I leave this open for visibility.

[JakubHelis]

@cytopia Reinstall of Devilbox fix reported error (for me )

[alzen8work]

[alzen8work]

so what may be the action plan? revert to old docker?

[cytopia]

@alzen8work are you using this version? If so, then revert to a previous minor version

[alzen8work]

[alzen8work]

@alzen8work are you using this version? If so, then revert to a previous minor version

i have downgrade to Docker 18.03.1-ce win65

[alzen8work]

https://docs.docker.com/docker-for-windows/release-notes/

the ones i tried:
Docker Community Edition 18.03.1-ce-win65 2018-04-30
Docker Community Edition 18.06.0-ce-win70 2018-07-25
Docker Community Edition 18.06.0-ce-win72 2018-07-26
Docker Community Edition 18.06.1-ce-win73 2018-08-29

all so far is not working

[cytopia]

@alzen8work what is the name of your Devilbox directory? Does it start with underscores? If so, it must start with [a-zA-Z0-9].

[alzen8work]

the name is __dvbx_20181001

i've change it to dvbx_20181001, and it seems is working already

[alzen8work]

ive use the branch called docker-volume not sure whether it is the correct branch to play ard though

[cytopia]

ive use the branch called docker-volume not sure whether it is the correct branch to play ard though

Yes, this is going to be (at least for Windows) the new branch for the Devilbox. I will merge it once it has been thoroughly tested.