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

Question

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

ststeiger opened this issue 4 years ago · comments

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...

Stefan Steiger · Answer 1 · Wed Jun 03 2020 17:33:51 GMT+0800 (China Standard Time)

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/

Stefan Steiger · Answer 2 · Wed Jun 03 2020 17:42:12 GMT+0800 (China Standard Time)

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 · Answer 3 · Fri Jul 03 2020 02:53:17 GMT+0800 (China Standard Time)

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

Had to do this three times now because of permissions.

Mostafa · Answer 4 · Sat Dec 05 2020 01:38:34 GMT+0800 (China Standard Time)

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]

Mostafa · Answer 5 · Sat Dec 05 2020 01:52:44 GMT+0800 (China Standard Time)

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

Emmanuel Caamal · Answer 6 · Fri Dec 11 2020 12:00:51 GMT+0800 (China Standard Time)

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

Mateusz · Answer 7 · Wed Jan 06 2021 22:51:27 GMT+0800 (China Standard Time)

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

Tarun Tiwari · Answer 8 · Sat Jan 16 2021 07:54:30 GMT+0800 (China Standard Time)

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?

Isaack Rasmussen · Answer 9 · Mon May 03 2021 06:00:35 GMT+0800 (China Standard Time)

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

Jéan Roux · Answer 10 · Sun Jun 13 2021 05:19:00 GMT+0800 (China Standard Time)

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 · Answer 11 · Mon Jun 14 2021 20:24:40 GMT+0800 (China Standard Time)

@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

Asad Ali · Answer 12 · Sat Jul 03 2021 01:31:39 GMT+0800 (China Standard Time)

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

Alex Cunha · Answer 13 · Wed Oct 06 2021 03:17:35 GMT+0800 (China Standard Time)

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.

Amit Kumar · Answer 14 · Thu Oct 28 2021 18:47:29 GMT+0800 (China Standard Time)

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 :-)

Wodson Correia · Answer 15 · Tue Dec 28 2021 09:24:42 GMT+0800 (China Standard Time)

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

Adolfo Mazariegos · Answer 16 · Fri Apr 29 2022 01:50:35 GMT+0800 (China Standard Time)

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...

Pedro Salinas-Ruiz · Answer 17 · Fri Jul 22 2022 04:27:29 GMT+0800 (China Standard Time)

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.

Thomas Sondergaard · Answer 18 · Tue Sep 27 2022 21:32:27 GMT+0800 (China Standard Time)

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 · Answer 19 · Mon Oct 10 2022 23:10:38 GMT+0800 (China Standard Time)

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.

Osni Pezzini Junior · Answer 20 · Fri Nov 11 2022 06:56:32 GMT+0800 (China Standard Time)

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

Kristian Bendrén · Answer 21 · Sun Mar 12 2023 02:00:10 GMT+0800 (China Standard Time)

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`