SQL-Server 2019 docker container fails to start with -v option #615

ststeiger · 2020-06-03T08:47:02Z

I'm trying to run SQL-Server 2019 in docker in Ubuntu 18.04.

This is how I want it to look:

mkdir -p /var/opt/mssql_2019
docker run -d -p 2019:1433 --name mssql_2019 -e 'MSSQL_SA_PASSWORD=TopSecret123456!abc' -e 'ACCEPT_EULA=Y' -e MSSQL_PID="Developer" -v /var/opt/mssql_2019:/var/opt/mssql -d mcr.microsoft.com/mssql/server:2019-latest

I issue the command, and sql-server exits immediately, not even an entry in the logfile in /var/opt/mssql_2019, hell, not even a file created there.
If I omit
-v /var/opt/mssql_2019:/var/opt/mssql

then it works fine.

Doing exactly the same with sql-server 2017 worked fine.

I run docker logs <containterID> and I get

SQL-Server 2019 will run as non-root by default. 
This container is running as user mssql. 
To learn more, visit...
/opt/mssql/bin/sqlservr: Error: The system directory [/.system] could not be created. Error [13].

I set permisson on /var/opt/mssql_2019 for group mssql to read&write...

Am I doing something wrong here, or is this a bug ?

If this is a permission issue, how can I get the container to run as root ?

If I switch to su mssql, I can create and delete files and folders in /var/opt/mssql_2019 without problems.

Also, if I add user mssql to sudo
adduser mssql sudo
that doesn't help.

It should be noted that the docker file says

RUN useradd -M -s /bin/bash -u 10001 -g 0 mssql
RUN mkdir -p -m 770 /var/opt/mssql && chgrp -R 0 /var/opt/mssql

but on my computer, user mssql already exists as user 999...
Probably added by sql-server 2017...

The text was updated successfully, but these errors were encountered:

ststeiger · 2020-06-03T09:33:51Z

Solved, don't know which one of the following did the trick
Rename the existing mssql user to mssql_2017
Add user mssql, add to group 0
Add permissions to /var/opt/mssql_2019 and /var/opt/mssql.

Maybe it would have sufficed to just chgrp -R 0 /var/opt/mssql_2019

usermod --login mssql_2017 mssql
useradd -M -s /bin/bash -u 10001 -g 0 mssql

chgrp -R 0 /var/opt/mssql
chgrp -R 0 /var/opt/mssql_2019

from dockerfile excerpt in
https://blog.dbi-services.com/using-non-root-sql-server-containers-on-docker-and-k8s/

ststeiger · 2020-06-03T09:42:12Z

Maybe it either should check if the user already exists, or it should create a separate user for every mssql-version. Don't know if the docker stuff uses the id or the username for permisson.

SonGokussj4 · 2020-07-02T18:53:17Z

mkdir mssql && cd mssql
mkdir data
chown 10001 data
Run container

Had to do this three times now because of permissions.

mostafa8026 · 2020-12-04T17:38:34Z

I have this issue in k8s. :((

 # k logs mssql-57f6f78dbb-4jwwk
SQL Server 2019 will run as non-root by default.
This container is running as user mssql.
To learn more visit https://go.microsoft.com/fwlink/?linkid=2099216.
/opt/mssql/bin/sqlservr: Error: The system directory [/.system] could not be created.  Errno [13]

mostafa8026 · 2020-12-04T17:52:44Z

Problem has been resolve with running this command in the host:
chown 10001:0 [the-path-of-the-mounted-volume]

emmanuelcaamal · 2020-12-11T04:00:51Z

I had the same problem, I solved it in the following way.

my docker compose was has follows


sqlserver:
    container_name: "sqlserver"
    hostname: "sqlserver"
    image: "mcr.microsoft.com/mssql/server"
    environment: 
        SA_PASSWORD: "<my_password_here>"
        ACCEPT_EULA: "Y"
    ports:
        - 2533:1433
    volumes:
        - /var/lib/docker/volumes/mssql_db/_data:/var/opt/mssql
    expose:
        - 2533

and the change that applies was the following

- /var/lib/docker/volumes/mssql_db/_data:/var/opt/data

finally this worked

GetoXs · 2021-01-06T14:51:27Z

There are few solution for this problem:

1. Run docker as root.

eg. compose:

version: '3.6'
services:
  mssql:
    image: mcr.microsoft.com/mssql/server:2019-latest
    user: root
    ports:
      - 1433:1433
    environment:
      - ACCEPT_EULA=Y
      - SA_PASSWORD=BLAH
    volumes:
      - ./data:/var/opt/mssql/data

Source: #13 (comment)

2. Setup proper directory owner (mssql)

Check id for mssql user on docker image
sudo docker run -it mcr.microsoft.com/mssql/server id mssql
gives: uid=10001(mssql) gid=0(root) groups=0(root)
Change folder's owner
sudo chown 10001 VOLUME_DIRECTORY

Source in spanish: https://www.eiximenis.dev/posts/2020-06-26-sql-server-docker-no-se-ejecuta-en-root/

3. Full access (not recommended)

Give full access to db files on host
sudo chmod 777 -R VOLUME_DIRECTORY

tmtiwari · 2021-01-15T23:54:30Z

I have this issue in k8s. :((

 # k logs mssql-57f6f78dbb-4jwwk
SQL Server 2019 will run as non-root by default.
This container is running as user mssql.
To learn more visit https://go.microsoft.com/fwlink/?linkid=2099216.
/opt/mssql/bin/sqlservr: Error: The system directory [/.system] could not be created.  Errno [13]

And, when I change the mapping to /var/opt/mssql/data I get this :

This container is running as user mssql.
To learn more visit https://go.microsoft.com/fwlink/?linkid=2099216.
2021-01-15 23:50:05.95 Server      Setup step is copying system data file 'C:\templatedata\master.mdf' to '/var/opt/mssql/data/master.mdf'.
2021-01-15 23:50:06.05 Server      ERROR: Setup FAILED copying system data file 'C:\templatedata\master.mdf' to '/var/opt/mssql/data/master.mdf':  2(The system cannot find the file specified.)
ERROR: BootstrapSystemDataDirectories() failure (HRESULT 0x80070002)

Why is an Ubuntu image looking in C: drive for template data?

IsaackRasmussen · 2021-05-02T22:00:35Z

For Kubernetes: Adding the SecurityContext also works
https://docs.microsoft.com/en-us/sql/linux/tutorial-sql-server-containers-kubernetes?view=sql-server-ver15

IoTPlay · 2021-06-12T21:19:00Z

What about rather running as another user? I cannot get this to work.

version: '3.6'
services:
  mssql:
    image: mcr.microsoft.com/mssql/server:2019-latest
    user: mylinuxuser   # not as root
    ....

amvin87-zz · 2021-06-14T12:24:40Z

@IoTPlay only the user mssql is supported to run SQL Server on Linux. See this sample for example: https://github.com/microsoft/mssql-docker/blob/master/linux/preview/SLES/dockerfile

asadalidev · 2021-07-02T17:31:39Z

Problem has been resolve with running this command in the host:
chown 10001:0 [the-path-of-the-mounted-volume]

it saved my time. Thanks

alercunha · 2021-10-05T19:17:35Z

In my case this error happened because the OS drive was full. Somehow this error occurred because of that.
Just posting here in case someone is looking for an alternate solution.

amkuio · 2021-10-28T10:47:29Z

Problem has been resolve with running this command in the host: chown 10001:0 [the-path-of-the-mounted-volume]

Did the trick for me :-)

wodsonluiz · 2021-12-28T01:24:42Z

My docker compose. Running on Macos with m1 processor ✅

version: "3"
services:

  mssql:
    image: mcr.microsoft.com/azure-sql-edge
    ports:
      - 1433:1433
    environment:
      - ACCEPT_EULA=1
      - MSSQL_PID=Developer
      - MSSQL_USER=SA
      - SA_PASSWORD=mayPassword
    volumes:
      - ./data:/var/opt/mssql/data
    networks:
       - compose-network

networks:
  compose-network:
    driver: bridge

dieasmaz · 2022-04-28T17:50:35Z

I had the same problem, I solved it in the following way.

my docker compose was has follows
sqlserver:
    container_name: "sqlserver"
    hostname: "sqlserver"
    image: "mcr.microsoft.com/mssql/server"
    environment: 
        SA_PASSWORD: "<my_password_here>"
        ACCEPT_EULA: "Y"
    ports:
        - 2533:1433
    volumes:
        - /var/lib/docker/volumes/mssql_db/_data:/var/opt/mssql
    expose:
        - 2533
and the change that applies was the following

- /var/lib/docker/volumes/mssql_db/_data:/var/opt/data

finally this worked

This works for me!
Thanks...

okpedro · 2022-07-21T20:27:29Z

I'd recommend anyone facing this issue take a look at the following Microsoft documentation:
https://docs.microsoft.com/en-us/sql/linux/sql-server-linux-docker-container-security?view=sql-server-ver16

Take a look at the "Configure persistent storage permissions for non-root containers" section.

tsondergaard · 2022-09-27T13:32:27Z

When running with podman on RHEL 9 with selinux enabled, this is what fixed the problem for me:

chcon -t container_file_t /var/opt/mssql

amirkochak · 2022-10-10T15:10:38Z

In my case this error happened because the OS drive was full. Somehow this error occurred because of that. Just posting here in case someone is looking for an alternate solution.

Resolved the issue for me.

osnipezzini · 2022-11-10T22:56:32Z

Problem has been resolve with running this command in the host: chown 10001:0 [the-path-of-the-mounted-volume]

This solution fixed for me

kristianbendren · 2023-03-11T18:00:10Z

For me it helped by setting the user:root

Part of my docker-compose
`version: '3.4'

services:
mssql:
container_name: mssql
image: 'mcr.microsoft.com/mssql/server:2022-latest'
user: root
hostname: mssql
networks:
- proxy
volumes:
- /volume1/docker-data/mssql/data:/var/opt/mssql/data`

m4ss1m0g · 2024-02-06T11:40:35Z

For Docker Desktop, WSL2 and docker volumes the solution is:

run the image with -u 0:0 flag docker run -u 0:0 ..... mcr.microsoft.com/mssql/server:2022-latest
enter the container with bash and cd to /var/opt
run chown -R 10001:0 mssql
remove the container and re-start it without -u 0:0

ryepup · 2024-05-25T17:42:23Z

I ran into this using docker volumes, and didn't want to run mssql as root. where I can't easily chown.

This is what I ended up with:

version: "3.7"

services:
  mssql:
    image: mcr.microsoft.com/mssql/server:2022-latest
    restart: always # keep trying, fix-perms might fix mssql
    environment:
      ACCEPT_EULA: "Y"
      MSSQL_SA_PASSWORD: "<password>"
    volumes:
      - "mssql-data:/var/opt/mssql/data"

  # mssql has some weird defaults around permissions; fixup the volume to match
  fix-perms:
    image: mcr.microsoft.com/mssql/server:2022-latest
    user: root
    command: chown -R mssql:root /var/opt/mssql
    volumes:
      - "mssql-data:/var/opt/mssql/data"

volumes:
  mssql-data:

amvin87-zz closed this as completed Jun 14, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

SQL-Server 2019 docker container fails to start with -v option #615

SQL-Server 2019 docker container fails to start with -v option #615

ststeiger commented Jun 3, 2020 •

edited

ststeiger commented Jun 3, 2020 •

edited

ststeiger commented Jun 3, 2020 •

edited

SonGokussj4 commented Jul 2, 2020

mostafa8026 commented Dec 4, 2020

mostafa8026 commented Dec 4, 2020 •

edited

emmanuelcaamal commented Dec 11, 2020 •

edited

GetoXs commented Jan 6, 2021

tmtiwari commented Jan 15, 2021

IsaackRasmussen commented May 2, 2021

IoTPlay commented Jun 12, 2021

amvin87-zz commented Jun 14, 2021

asadalidev commented Jul 2, 2021

alercunha commented Oct 5, 2021 •

edited

amkuio commented Oct 28, 2021

wodsonluiz commented Dec 28, 2021 •

edited

dieasmaz commented Apr 28, 2022

okpedro commented Jul 21, 2022

tsondergaard commented Sep 27, 2022

amirkochak commented Oct 10, 2022

osnipezzini commented Nov 10, 2022

kristianbendren commented Mar 11, 2023

m4ss1m0g commented Feb 6, 2024

ryepup commented May 25, 2024

SQL-Server 2019 docker container fails to start with -v option #615

SQL-Server 2019 docker container fails to start with -v option #615

Comments

ststeiger commented Jun 3, 2020 • edited

ststeiger commented Jun 3, 2020 • edited

ststeiger commented Jun 3, 2020 • edited

SonGokussj4 commented Jul 2, 2020

mostafa8026 commented Dec 4, 2020

mostafa8026 commented Dec 4, 2020 • edited

emmanuelcaamal commented Dec 11, 2020 • edited

GetoXs commented Jan 6, 2021

1. Run docker as root.

2. Setup proper directory owner (mssql)

3. Full access (not recommended)

tmtiwari commented Jan 15, 2021

IsaackRasmussen commented May 2, 2021

IoTPlay commented Jun 12, 2021

amvin87-zz commented Jun 14, 2021

asadalidev commented Jul 2, 2021

alercunha commented Oct 5, 2021 • edited

amkuio commented Oct 28, 2021

wodsonluiz commented Dec 28, 2021 • edited

dieasmaz commented Apr 28, 2022

okpedro commented Jul 21, 2022

tsondergaard commented Sep 27, 2022

amirkochak commented Oct 10, 2022

osnipezzini commented Nov 10, 2022

kristianbendren commented Mar 11, 2023

m4ss1m0g commented Feb 6, 2024

ryepup commented May 25, 2024

ststeiger commented Jun 3, 2020 •

edited

ststeiger commented Jun 3, 2020 •

edited

ststeiger commented Jun 3, 2020 •

edited

mostafa8026 commented Dec 4, 2020 •

edited

emmanuelcaamal commented Dec 11, 2020 •

edited

alercunha commented Oct 5, 2021 •

edited

wodsonluiz commented Dec 28, 2021 •

edited