Error during startup: /proc/10/maps: Permission denied

[collinsauve]

Hello! I am attempting to update from the microsoft/mssql-server-linux:2017-CU8 image to mcr.microsoft.com/mssql/server:2019-GA-ubuntu-16.04. I get an error during startup that has a lot of "Permission denied" on various /proc files.

I am using Docker for Windows with a Docker Compose file (some paths/password redacted):

version: '3'
services:
  sql:
    image: mcr.microsoft.com/mssql/server:2019-GA-ubuntu-16.04
    restart: always
    environment:
     - ACCEPT_EULA=Y
     - SA_PASSWORD=Password123
     - MSSQL_PID=Developer
    volumes:
     - c:\\ProgramData\\myfolder\\sql\\:/var/opt/mssql/
    ports:
     - "11433:1433"
networks:
  default:
    external:
      name: mynetwork

Full log is attached.

log.txt

[collinsauve]

P.S. in case it is relevant:

$ docker --version
Docker version 19.03.5, build 633a0ea

$ systeminfo | findstr //B //C:"OS Name" //C:"OS Version"
OS Name:                   Microsoft Windows 10 Pro
OS Version:                10.0.18363 N/A Build 18363

[michaelherndon]

I got this today. I was on the docker tech preview. though it had to do with beta bits since I had edge docker installed. Downgraded docker. Changed to mssql 2017, different errors, dug into the log files found things on Kernel Bug check.

Anyways, It has to do with mounting. You can't mount the /var/opt/mssql volume on Windows. You can only mount to the subfolders e.g.

• /var/opt/mssql/data
• /var/opts/mssql/log,
• /var/opt/mssql/secrects

https://docs.microsoft.com/en-us/sql/linux/sql-server-linux-configure-docker?view=sql-server-ver15#mount-a-host-directory-as-data-volume

[rivaldi8]

This issue seems to be caused by newer versions of the kernel. Version 6.5 works, but 6.7 and 6.8 don't (I haven't tested with 6.6).

[rubbengimenez]

This issue seems to be caused by newer versions of the kernel. Version 6.5 works, but 6.7 and 6.8 don't (I haven't tested with 6.6).

Hi! Did you find any solutions using newer kernel versions?

[rivaldi8]

No, in fact I'm stuck in the previous Ubuntu version because of this. I see version 6.10 is already available and 6.11almost ready. I'll try the last available when I reboot my computer someday and report back.

[rubbengimenez]

No, in fact I'm stuck in the previous Ubuntu version because of this. I see version 6.10 is already available and 6.11almost ready. I'll try the last available when I reboot my computer someday and report back.

Have you tried with a newer image version?

In my case, I was using 2019-CU14-ubuntu-20.04 and upgrading to 2019-CU28-ubuntu-20.04 did the trick. I'm using kernel version 6.8.

[ramita-0]

No, in fact I'm stuck in the previous Ubuntu version because of this. I see version 6.10 is already available and 6.11almost ready. I'll try the last available when I reboot my computer someday and report back.

Have you tried with a newer image version?

In my case, I was using 2019-CU14-ubuntu-20.04 and upgrading to 2019-CU28-ubuntu-20.04 did the trick. I'm using kernel version 6.8.

Thanks! I'm also running kernel v6.8. I was using 2022-preview-ubuntu-22.04 and could not run the container; and with 2022-latest it worked.

[rivaldi8]

Have you tried with a newer image version?

No, I hadn't tried, but now I've been testing different versions. I've had some weird issues with the latest (CU28), so I've been testing some versions in between. Finally the 2019-CU26-ubuntu-20.04 has worked for me. Thanks!