-
Notifications
You must be signed in to change notification settings - Fork 8.8k
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
MacOS - Error: 17113, Severity: 16, State: 1. #160
Comments
When reading
So without volume mapping it works. |
How to solve this? |
[@thearabbit] I am assuming that you are trying to run the SQL Server Docker image on Mac.
As @jodebrui mentioned we will need more details on what you are trying to do so we can further assist. Thanks, |
I run docker run --name mssql-container -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=123456' -p 1433:1433 -d microsoft/mssql-server-linux It show Configuring Microsoft(R) SQL Server(R)...
Microsoft(R) SQL Server(R) setup failed with error code 1. Please check the setup log in /var/opt/mssql/log for more information. |
I get the same error
|
After adding /var/opt/mssql as a volume and inspecting the path on the container I found out that in my case it was a password that was to simple.
If you use mac, use screen to get to the to the tty Run screen
Get inside Run your container
Check path: Show error log (container id will be different for you) |
Now it work fine. |
2017-03-09 20:17:40.13 Server UTC adjustment: 0:00 I am facing this problem when i push the docker image to heroku container registry |
I use Mac, with Docker:This is an evaluation version. There are [145] days left in the evaluation period. Please help me... |
this is still happening in mac the same error any help will be appreciated
|
Reproducing this error. Kinda useless error message. I give up. |
got this too |
I am running docker
1.12.3
on macOS El Capitan.Docker can use 9GB Ram of total 16GB.
When I run:
It gives me the Error message:
I have mounted the /var/opt/ to my host and when I
cat
the logfile it says:cat ~/docker/mssql/opt/log/errorlog
The text was updated successfully, but these errors were encountered: