Skip to content

Commit e389578

Browse files
authored
minor readability edits
1 parent ae17691 commit e389578

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -92,10 +92,12 @@ docker exec -d mssql-server /opt/mssql-tools/bin/sqlcmd -S . -U sa -P "$pw" -Q "
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

9494
If you receive this error when running the last command:
95+
9596
```
9697
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
9798
```
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+
100+
It's likely that the folder `/opt/mssql-tools/bin/sqlcmd` does not exist. Open Docker Desktop, select your SQL Server Docker container, select Files and browse for the mssql-tools folder. This folder might have a different name, such as `/opt/mssql-tools18/bin/sqlcmd`. Update the last line of code accordingly and run it gain.
99101

100102
> [!NOTE]
101103
> 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`.

0 commit comments

Comments
 (0)