-
-
Notifications
You must be signed in to change notification settings - Fork 654
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Win10] Updating from 18.06.0-ce to 18.06.1-ce crashes all set of containers #374
Comments
@gpimentelv thanks for reporting this. I leave this open for visibility. |
@cytopia Reinstall of Devilbox fix reported error (for me ) |
so what may be the action plan? revert to old docker? |
@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 |
https://docs.docker.com/docker-for-windows/release-notes/ the ones i tried: all so far is not working |
@alzen8work what is the name of your Devilbox directory? Does it start with underscores? If so, it must start with |
the name is __dvbx_20181001 i've change it to dvbx_20181001, and it seems is working already |
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. |
I am currently implementing CI checks against the last latest five versions of Docker and last latest five versions of Docker-Compose (So additional 25 parallel jobs on Travis-CI). This however will only catch errors on Linux: #430 If you guys know of any other CI systems that provide Docker+Windows and/or Docker+Mac as a backend I will be happy to implement an equivalent as well. |
@gpimentelv, OK I will close this one then.
@alzen8work, You should go on that branch here from now on: #416 |
appveyor has windows Ci. no idea about the docker |
ISSUE TYPE
OS / ENVIRONMENT
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:
BUT THEN
EXPECTED BEHAVIOUR
ACTUAL BEHAVIOUR
OTHER INFORMATION
The text was updated successfully, but these errors were encountered: