Skip to content

Commit ae17691

Browse files
Update quickstart-mssql.md
Added a description for an update I had to make on the command to create a database on the SQL Server Docker container. The mssql-tools folder did not exist, it was mssql-tools18.
1 parent 99d45f3 commit ae17691

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

articles/azure-functions/durable/quickstart-mssql.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -91,6 +91,12 @@ docker exec -d mssql-server /opt/mssql-tools/bin/sqlcmd -S . -U sa -P "$pw" -Q "
9191

9292
After you run these commands, you should have a local SQL Server running on Docker and listening on port 1443. If port 1443 conflicts with another service, you can rerun these commands after you change the variable `$port` to a different value.
9393

94+
If you receive this error when running the last command:
95+
```
96+
Error response from daemon: OCI runtime exec failed: exec failed: unable to start container process: exec: "/opt/mssql-tools/bin/sqlcmd": stat /opt/mssql-tools/bin/sqlcmd: no such file or directory: unknown
97+
```
98+
Then the likelihood is the folder `/opt/mssql-tools/bin/sqlcmd` does not exist, open Docker Desktop, click on your SQL Server Docker container, click on Files and browse for the mssql-tools folder. It's possible this folder has a differrent name, e.g. `/opt/mssql-tools18/bin/sqlcmd`. Update the last line of code accordingly and run it gain.
99+
94100
> [!NOTE]
95101
> To stop and delete a running container, you can use `docker stop <containerName>` and `docker rm <containerName>` respectively. You can use these commands to re-create your container and to stop the container when you finish this quickstart. For more assistance, run `docker --help`.
96102

0 commit comments

Comments
 (0)