Post reply

Stairway to Database Containers Level 2: Persisting Storage in Containers

  • February 25, 2019 at 12:00 am

    #3660354

    Comments posted to this topic are about the item Stairway to Database Containers Level 2: Persisting Storage in Containers

  • January 3, 2020 at 4:10 am

    #3712026

    When I try to run a second container

    C:\WINDOWS\system32>docker container run -e "SA_PASSWORD=whatever" -p 1433:1433 --name Sql2019e -e "ACCEPT_EULA=Y" -d mcr.microsoft.com/mssql/server

    8684c513f35502fec959071b2e688fe760d383700d2bee3a6d0188e2b251bb08

    docker: Error response from daemon: driver failed programming external connectivity on endpoint Sql2019e (bca266a1b96c89575e8ef94268f4ab4a9861075785d4f3ba335265f535055286): Bind for 0.0.0.0:1433 failed: port is already allocated.

    So I change the port

    C:\WINDOWS\system32>docker container run -e "SA_PASSWORD=litso$47" -p 1434:1433 --name Sql2019g -e "ACCEPT_EULA=Y" -d mcr.microsoft.com/mssql/server

    78a82452150bea3b7e3ad29f619631ce1f661d5a0a3515b6c88639eae42d77e7

    C:\WINDOWS\system32>docker container ls

    CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

    78a82452150b mcr.microsoft.com/mssql/server "/opt/mssql/bin/perm…" 12 seconds ago Up 11 seconds 0.0.0.0:1434->1433/tcp Sql2019g

    03f3fca07f24 mcr.microsoft.com/mssql/server "/opt/mssql/bin/perm…" 21 minutes ago Up 13 minutes 0.0.0.0:1433->1433/tcp Sql2019b

    Now I get "cannot connect to (local):1434 Named Pipes error 40 etc.

  • January 3, 2020 at 7:17 pm

    #3712208

    You should be connecting with TCP/IP, not named pipes here. Names pipes aren't using these ports.

     

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply