-
Notifications
You must be signed in to change notification settings - Fork 758
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
ERROR: BootstrapSystemDataDirectories() failure (HRESULT 0x80070001) #602
Comments
just noticed the same here. |
Same issue here. |
Ditto |
I think this is related the issue where the latest version of docker has problems with volumes: |
Same issue |
This theory stacks up. My other containers running as they were in 2.3.0.2 don't connect to any external volumes. |
I uninstalled 2.3.0.2 and installed 2.2.0.5 so all back up and running. To save you a search, you can download it here |
Docker response: This is a regression in Docker. We will fix it. This ticket can be duped against docker/for-win#6646. |
… occurrs on the most recent version of Docker for Windows. It'll work when it's fixed... microsoft/mssql-docker#602
I'm having the same issue in #542 -> #542 (comment) |
Versions
OS: Windows 10 Pro 64 Bit 1909 (18363.836)
Docker desktop version: 2.3.0.2 (45183)
Engine: 19.03.8
Compose: 1.25.5
Kubernetes: 1.16.5
I've successfully been using an MSSQL docker container for over a month now. It's based on image 'mcr.microsoft.com/mssql/server:2019-CU2-ubuntu-16.04' and auto starts up via docker-compose up using the following docker-compose.yml file:
Ever since I upgraded my Docker desktop version, to the one listed above, the container's constantly showing as restarting:
docker container ls -a
When I look at the container logs it's showing:
I wasn't sure if this was a permissions issue but changing the yml to:
Just ended up with the container restarting and the logs showing:
I've done windows updates incase there was an update needed to run on the new version of docker desktop. I've also tried deleting the container and image but I'm still getting the same error and the container won't stay running.
I noticed someone else had the same error here but this seemed to be linked to an issue declaring the volume name.
My issue is something stopping working that has been working well for a number of weeks.
Also, the other containers I have in docker are running as they were before the upgrade.
Any ideas?
The text was updated successfully, but these errors were encountered: