Carlos Robles

> > sudo docker run --name honeywell --hostname SQL --network="docker-network" --ip=172.18.0.8 -p 1434:1433 -e 'sa_password=Xkp7VmE6YHVDM' -e 'ACCEPT_EULA=Y' -d microsoft/mssql-server-linux:latest > > docker inspect -f "{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}" honeywell > > 172.18.0.8...

@Hal1987 Just checking, was your issue solved with the example above? If so, I think this issue can be closed :)

This looks like the typical message you will see when someone or something is trying to scan/use the SQL Server port. Does anyone have any sort of Antivirus scanning the...

I experienced this issue in the past, the best workaround I found so far is to use an env variable for the sleep command. A container does not take the...

> The main problem is that there is no sudo which is need by mssql-conf. > Message: : ./mssql-conf: line 28: sudo: command not found Fortunately, you don't need the...

> @dbsmaster: the environment variables are correctly set. After looking into the log mssql files, it seems, that the agent canont connect to the server (no reason given). This would...

> Even with a hostname of 5 letters still the same problem. > Extract of sqlagent.out: > > ``` > 2020-05-03 19:01:32 - ! [150] SQL Server does not accept...

Hello there, Have anyone tried to use the latest image of SQL Server 2019? **mcr.microsoft.com/mssql/server:2019-CU3-ubuntu-18.04** I was checking the thread, it is from August 2019. Based on the release cycle,...

Hello there, This issue could be caused by your containers taking some time to get SQL Server started. Of course, It depends of your Docker daemon resources and configuration. But...

> EnableRetryOnFailure Cool!! That's pretty much what I do with Flyway to perform database migrations 😄