Docker Desktop Keeps Hanging after first installing- Fedora 39

I recently moved on to use Fedora 39 and installed docker successfully after following the guidelines on the official install guide.

I managed to setup an MSSQL image and it worked perfectly at the time of the tests that I was doing.

Unfortunately after restarting it just stopped responding properly, it was really slow , kept hanging and kept asking to wait or force quit over and over again.

I reinstalled it from scratch again, and managed to get it working properly.

After restarting the computer again it simply started misbehaving again.

I have been trying to troubleshoot it myself but the only thing that works is reinstalling it from scratch again and again.

cat /etc/os-release
NAME="Fedora Linux"
VERSION="39 (Workstation Edition)"
ID=fedora
VERSION_ID=39
VERSION_CODENAME=""
PLATFORM_ID="platform:f39"
PRETTY_NAME="Fedora Linux 39 (Workstation Edition)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:39"
DEFAULT_HOSTNAME="fedora"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f39/system-administrators-guide/"
SUPPORT_URL="https://ask.fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=39
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=39
SUPPORT_END=2024-11-12
VARIANT="Workstation Edition"
VARIANT_ID=workstation
docker --version
Docker version 25.0.3, build 4debf41

I finally found this script that is included in the app and it appears that one of the processes that it uses might not be running? I’m unsure on how to fix this and I havent found anything else in the internet about how to fix this.

$ /opt/docker-desktop/bin/com.docker.diagnose check
Starting diagnostics

[2024-02-27T03:09:29.321399170Z][com.docker.diagnose.ipc][I] ipc.NewClient: 096dc69f-diagnose -> <HOME>/.docker/desktop/backend.sock BackendAPI
[2024-02-27T03:09:29.321536282Z][com.docker.diagnose.ipc][I] (95aa95f6) 096dc69f-diagnose C->S BackendAPI POST /idle/make-busy
[2024-02-27T03:09:29.322095149Z][com.docker.diagnose.ipc][I] (95aa95f6) 096dc69f-diagnose C<-S 8ada269e-BackendAPI POST /idle/make-busy (550.3µs): 0xc00064ae60
[2024-02-27T03:09:30.321954300Z][com.docker.diagnose.ipc][I] (28c45822) 096dc69f-diagnose C->S BackendAPI GET /idle
[2024-02-27T03:09:30.322866170Z][com.docker.diagnose.ipc][I] (28c45822) 096dc69f-diagnose C<-S 8ada269e-BackendAPI GET /idle (824.864µs): {"apisInFlight":{},"booted":true,"busyReason":["timed activities: map[/idle/make-busy:28.999519002s dial//run/guest-services/volume-contents.sock:53.334777684s read//run/guest-services/volume-contents.sock:53.335322214s write//run/guest-services/volume-contents.sock:53.337502675s]"],"containers":0,"idle":"bool","kubernetesEnabled":false,"reduced":false,"services":0,"timedActivities":{"/idle/make-busy":"float64","dial//run/guest-services/volume-contents.sock":53334777684,"read//run/guest-services/volume-contents.sock":53335322214,"write//run/guest-services/volume-contents.sock":53337502675},"vmPaused":false,"vmRunning":true,"vmStopped":false,"windowsContainers":false}
[PASS] DD0039: are KVM user permissions configured?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0031: does the Docker API work?
[PASS] DD0013: is the $PATH ok?
[PASS] DD0034: is Context set to a Docker Desktop context?
[PASS] DD0003: is the Docker CLI working?
[PASS] DD0038: is the connection to Docker working?
[FAIL] DD0014: are the backend processes running? querying com.docker.backend process: is it running as a different user?: readlink /proc/4853/exe: permission denied
[FAIL] DD0007: is the backend responding? prereq failed: are the backend processes running?
[FAIL] DD0009: is the vpnkit API responding? prereq failed: are the backend processes running?
[FAIL] DD0010: is the Docker API proxy responding? prereq failed: are the backend processes running?
[SKIP] DD0030: is the image access management authorized?
[PASS] DD0037: is the virtiofs setup correct?
[PASS] DD0036: is the credentials store configured correctly?
[PASS] DD0033: does the host have Internet access?
[PASS] DD0039: are KVM user permissions configured?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0031: does the Docker API work?
[PASS] DD0032: do Docker networks overlap with host IPs?

Please investigate the following 1 issue:

1 : The test: are the backend processes running?
    Failed with: querying com.docker.backend process: is it running as a different user?: readlink /proc/4853/exe: permission denied

Not all of the backend processes are running.

Since Docker Desktop runs Docker in a virtual machine, I don’t think you could fix the process directly. I installed Docker DEsktop for Linux only on Ubuntu 22.04. Somehow it always worked, except at the very beginning of the desktop on Linux.

There was a similar issue with this error message on Mac

They recommended upgrading Docker Desktop to a newer version. You shared the version of Docker but not Docker Desktop.

This command shows the version of Docker Desktop

docker version --format '{{ .Server.Platform.Name }}'

Alternatively, if you don’t need the features of Docker Desktop, you can run Docker CE natively on Linux

I ended up going for the docker CE directly and a basic UI manager like Portainer for other things. I have not been able to setup an Image for MsSQL successfully, I’m not really sure as of why. But most of anything else is working properly. Other Images are working, like nodejs. The weird thing to me is that on the very first day of installation everything was working smoothly and properly regarding Docker Desktop. And docker Desktop was up to date, as It had just been installed that specific day from the rpm package provided by the docs. All the requirements were met. It just ran properly once then it did not. Either way, I moved on from it and I’m just using Docker CE.

My problem now is that it doesnt want to run the MSSQL image for some reason.

I was just doing the following command:

$ docker run -e "ACCEPT_EULA=Y" -e "MSSQL_SA_PASSWORD=serviceMSSQL-001" -p 1433:1433 --name ipesah_mssql --network ipesah_services -d mcr.microsoft.com/mssql/server:2022-latest

Or just the one that’s recomended by microsoft on the image’s docs with ab actual password.

$ docker run -e "ACCEPT_EULA=Y" -e "MSSQL_SA_PASSWORD=yourStrong(!)Password" -p 1433:1433 -d mcr.microsoft.com/mssql/server:2022-latest

2024-02-29 17:46:24.60 Server      Did not find an existing master data file /var/opt/mssql/data/master.mdf, copying the missing default master and other system database files. If you have moved the database location, but not moved the database files, startup may fail. To repair: shutdown SQL Server, move the master database to configured location, and restart.

2024-02-29 17:46:24.60 Server      Setup step is copying system data file 'C:\templatedata\mastlog.ldf' to '/var/opt/mssql/data/mastlog.ldf'.

2024-02-29 17:46:24.61 Server      Setup step is copying system data file 'C:\templatedata\model.mdf' to '/var/opt/mssql/data/model.mdf'.

2024-02-29 17:46:24.62 Server      Setup step is copying system data file 'C:\templatedata\modellog.ldf' to '/var/opt/mssql/data/modellog.ldf'.

2024-02-29 17:46:24.63 Server      Setup step is copying system data file 'C:\templatedata\msdbdata.mdf' to '/var/opt/mssql/data/msdbdata.mdf'.

2024-02-29 17:46:24.64 Server      Setup step is copying system data file 'C:\templatedata\msdblog.ldf' to '/var/opt/mssql/data/msdblog.ldf'.

2024-02-29 17:46:24.64 Server      Setup step is FORCE copying system data file 'C:\templatedata\model_replicatedmaster.mdf' to '/var/opt/mssql/data/model_replicatedmaster.mdf'.

2024-02-29 17:46:24.65 Server      Setup step is FORCE copying system data file 'C:\templatedata\model_replicatedmaster.ldf' to '/var/opt/mssql/data/model_replicatedmaster.ldf'.

2024-02-29 17:46:24.65 Server      Setup step is FORCE copying system data file 'C:\templatedata\model_msdbdata.mdf' to '/var/opt/mssql/data/model_msdbdata.mdf'.

2024-02-29 17:46:24.67 Server      Setup step is FORCE copying system data file 'C:\templatedata\model_msdblog.ldf' to '/var/opt/mssql/data/model_msdblog.ldf'.

2024-02-29 17:46:24.69 Server      Microsoft SQL Server 2022 (RTM-CU11) (KB5032679) - 16.0.4105.2 (X64) 

	Nov 14 2023 18:33:19 

	Copyright (C) 2022 Microsoft Corporation

	Developer Edition (64-bit) on Linux (Ubuntu 22.04.3 LTS) <X64>

2024-02-29 17:46:24.69 Server      UTC adjustment: 0:00

2024-02-29 17:46:24.69 Server      (c) Microsoft Corporation.

2024-02-29 17:46:24.69 Server      All rights reserved.

2024-02-29 17:46:24.69 Server      Server process ID is 536.

2024-02-29 17:46:24.69 Server      Logging SQL Server messages in file '/var/opt/mssql/log/errorlog'.

2024-02-29 17:46:24.69 Server      Registry startup parameters: 

	 -d /var/opt/mssql/data/master.mdf

	 -l /var/opt/mssql/data/mastlog.ldf

	 -e /var/opt/mssql/log/errorlog

2024-02-29 17:46:24.70 Server      SQL Server detected 1 sockets with 8 cores per socket and 16 logical processors per socket, 16 total logical processors; using 16 logical processors based on SQL Server licensing. This is an informational message; no user action is required.

2024-02-29 17:46:24.70 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

2024-02-29 17:46:24.70 Server      Detected 12164 MB of RAM. This is an informational message; no user action is required.

2024-02-29 17:46:24.70 Server      Using conventional memory in the memory manager.

2024-02-29 17:46:24.70 Server      Detected pause instruction latency: 33 cycles.

2024-02-29 17:46:24.70 Server      SQL Server detected the following NUMA node configuration (NUMA Node number 0, Processor Group number 0, CPU Mask 0x000000000000ffff).

2024-02-29 17:46:24.70 Server      Page exclusion bitmap is enabled.

2024-02-29 17:46:24.75 Server      Buffer pool extension is not supported on Linux platform.

2024-02-29 17:46:24.76 Server      Buffer Pool: Allocating 2097152 bytes for 1234872 hashPages.

2024-02-29 17:46:24.87 Server      Buffer pool extension is already disabled. No action is necessary.

2024-02-29 17:46:25.14 Server      Installing Client TLS certificates to the store.

2024-02-29 17:46:25.15 Server      Error searching first file in /var/opt/mssql/security/ca-certificates: 3(The system cannot find the path specified.)

2024-02-29 17:46:25.15 Server      CPU vectorization level(s) detected:  SSE SSE2 SSE3 SSSE3 SSE41 SSE42 AVX AVX2 POPCNT BMI1 BMI2

2024-02-29 17:46:25.18 Server      Successfully initialized the TLS configuration. Allowed TLS protocol versions are ['1.0 1.1 1.2']. Allowed TLS ciphers are ['ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:!DHE-RSA-AES256-GCM-SHA384:!DHE-RSA-AES128-GCM-SHA256:!DHE-RSA-AES256-SHA:!DHE-RSA-AES128-SHA'].

2024-02-29 17:46:25.19 Server      Query Store settings initialized with enabled = 1, 

2024-02-29 17:46:25.20 Server      The maximum number of dedicated administrator connections for this instance is '1'

2024-02-29 17:46:25.20 Server      Node configuration: node 0: CPU mask: 0x000000000000ffff:0 Active CPU mask: 0x000000000000ffff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.

2024-02-29 17:46:25.23 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.

2024-02-29 17:46:25.23 Server      Lock partitioning is enabled.  This is an informational message only. No user action is required.

2024-02-29 17:46:25.25 Server      In-Memory OLTP initialized on lowend machine.

2024-02-29 17:46:25.26 Server      [INFO] Created Extended Events session 'hkenginexesession'

2024-02-29 17:46:25.26 Server      Database Instant File Initialization: enabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.

ForceFlush is enabled for this instance. 

2024-02-29 17:46:25.27 Server      Total Log Writer threads: 2. This is an informational message; no user action is required.

2024-02-29 17:46:25.27 Server      clwb is selected for pmem flush operation.

2024-02-29 17:46:25.28 Server      Software Usage Metrics is disabled.

2024-02-29 17:46:25.28 spid42s     [1]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1. ConcurrentGAMUpdate: 1. ConcurrentSGAMUpdate: 1, CleanupUnderUserTransaction: 0. TranLevelPVS: 0

2024-02-29 17:46:25.28 spid42s     Starting up database 'master'.

ForceFlush feature is enabled for log durability.

2024-02-29 17:46:25.31 spid42s     The tail of the log for database master is being rewritten to match the new sector size of 4096 bytes.  1024 bytes at offset 396288 in file /var/opt/mssql/data/mastlog.ldf will be written.

2024-02-29 17:46:25.33 Server      CLR version v4.0.30319 loaded.

2024-02-29 17:46:25.34 spid42s     Converting database 'master' from version 927 to the current version 957.

2024-02-29 17:46:25.34 spid42s     Database 'master' running the upgrade step from version 927 to version 928.
This program has encountered a fatal error and cannot continue running at Thu Feb 29 17:46:25 2024
The following diagnostic information is available:
         Reason: 0x00000001
         Signal: SIGABRT - Aborted (6)
          Stack:
                 IP               Function
                 ---------------- --------------------------------------
                 000055fdce704ce1 std::__1::bad_function_call::~bad_function_call()+0x96661
                 000055fdce7046a6 std::__1::bad_function_call::~bad_function_call()+0x96026
                 000055fdce703c2f std::__1::bad_function_call::~bad_function_call()+0x955af
                 00007f009fa70520 __sigaction+0x50
                 00007f009fac49fc pthread_kill+0x12c
                 00007f009fa70476 raise+0x16
                 00007f009fa567f3 abort+0xd3
                 000055fdce6d5d96 std::__1::bad_function_call::~bad_function_call()+0x67716
        Process: 9 - sqlservr
         Thread: 160 (application thread 0x278)
    Instance Id: cff1598d-2f40-4529-895c-cce11137c780
       Crash Id: 0fbacdd8-9172-4f9a-91ab-31cfe731e076
    Build stamp: a9299dd605c652a3cea4246273441bcfaf48afb4b482ab9dc43771eecaf6600b
   Distribution: Ubuntu 22.04.3 LTS
     Processors: 16
   Total Memory: 15944507392 bytes
      Timestamp: Thu Feb 29 17:46:25 2024
     Last errno: 22
Last errno text: Invalid argument
Capturing a dump of 9
Successfully captured dump: /var/opt/mssql/log/core.sqlservr.2_29_2024_17_46_25.9

2024-02-29 17:46:25.36 spid42s     Database 'master' running the upgrExecuting: /opt/mssql/bin/handle-crash.sh with parameters
     handle-crash.sh
     /opt/mssql/bin/sqlservr
     9
     /opt/mssql/bin
     /var/opt/mssql/log/
     
     cff1598d-2f40-4529-895c-cce11137c780
     0fbacdd8-9172-4f9a-91ab-31cfe731e076
     
     /var/opt/mssql/log/core.sqlservr.2_29_2024_17_46_25.9
Ubuntu 22.04.3 LTS
Capturing core dump and information to /var/opt/mssql/log...
/bin/cat: /proc/9/maps: Permission denied

Both container commands simply output this on the logs, after a while it just does this

find: '/proc/9/task/163/fdinfo': Permission denied
find: '/proc/9/task/164/fdinfo': Permission denied
find: '/proc/9/task/165/fdinfo': Permission denied
find: '/proc/9/task/166/fdinfo': Permission denied
find: '/proc/9/task/167/fdinfo': Permission denied
find: '/proc/9/task/168/fdinfo': Permission denied
find: '/proc/9/task/169/fdinfo': Permission denied
find: '/proc/9/task/170/fdinfo': Permission denied
find: '/proc/9/task/171/fdinfo': Permission denied
find: '/proc/9/task/172/fdinfo': Permission denied
find: '/proc/9/task/173/fdinfo': Permission denied
find: '/proc/9/task/174/fdinfo': Permission denied
find: '/proc/9/task/175/fdinfo': Permission denied
find: '/proc/9/task/176/fdinfo': Permission denied
find: '/proc/9/task/177/fdinfo': Permission denied
find: '/proc/9/task/178/fdinfo': Permission denied
find: '/proc/9/task/179/fdinfo': Permission denied
find: '/proc/9/task/180/fdinfo': Permission denied
find: '/proc/9/task/181/fdinfo': Permission denied
find: '/proc/9/task/182/fdinfo': Permission denied
find: '/proc/9/task/183/fdinfo': Permission denied
find: '/proc/9/task/184/fdinfo': Permission denied
find: '/proc/9/task/185/fdinfo': Permission denied
find: '/proc/9/task/186/fdinfo': Permission denied
find: '/proc/9/task/187/fdinfo': Permission denied
find: '/proc/9/task/188/fdinfo': Permission denied
find: '/proc/9/task/189/fdinfo': Permission denied
find: '/proc/9/task/190/fdinfo': Permission denied
find: '/proc/9/task/192/fdinfo': Permission denied
find: '/proc/9/task/193/fdinfo': Permission denied
find: '/proc/9/task/194/fdinfo': Permission denied
find: '/proc/9/task/195/fdinfo': Permission denied
find: '/proc/9/task/196/fdinfo': Permission denied
find: '/proc/9/task/197/fdinfo': Permission denied
find: '/proc/9/task/198/fdinfo': Permission denied
find: '/proc/9/task/199/fdinfo': Permission denied
find: '/proc/9/task/200/fdinfo': Permission denied
find: '/proc/9/task/201/fdinfo': Permission denied
find: '/proc/9/task/202/fdinfo': Permission denied
find: '/proc/9/task/203/fdinfo': Permission denied
find: '/proc/9/task/204/fdinfo': Permission denied
find: '/proc/9/task/205/fdinfo': Permission denied
find: '/proc/9/task/206/fdinfo': Permission denied
find: '/proc/9/task/207/fdinfo': Permission denied
find: '/proc/9/task/208/fdinfo': Permission denied
find: '/proc/9/task/209/fdinfo': Permission denied
find: '/proc/9/task/210/fdinfo': Permission denied
find: '/proc/9/task/211/fdinfo': Permission denied
find: '/proc/9/task/212/fdinfo': Permission denied
find: '/proc/9/task/213/fdinfo': Permission denied
find: '/proc/9/task/214/fdinfo': Permission denied
find: '/proc/9/task/215/fdinfo': Permission denied
find: '/proc/9/task/216/fdinfo': Permission denied
find: '/proc/9/task/217/fdinfo': Permission denied
find: '/proc/9/task/218/fdinfo': Permission denied
find: '/proc/9/task/219/fdinfo': Permission denied
find: '/proc/9/task/220/fdinfo': Permission denied
find: '/proc/9/task/221/fdinfo': Permission denied
find: '/proc/9/task/222/fdinfo': Permission denied
find: '/proc/9/task/223/fdinfo': Permission denied
find: '/proc/9/task/224/fdinfo': Permission denied
find: '/proc/9/task/225/fdinfo': Permission denied
find: '/proc/9/task/226/fdinfo': Permission denied
find: '/proc/9/task/227/fdinfo': Permission denied
find: '/proc/9/task/228/fdinfo': Permission denied
find: '/proc/9/task/229/fdinfo': Permission denied
find: '/proc/9/task/230/fdinfo': Permission denied
find: '/proc/9/task/231/fdinfo': Permission denied
find: '/proc/9/task/232/fdinfo': Permission denied
find: '/proc/9/task/233/fdinfo': Permission denied
find: '/proc/9/task/234/fdinfo': Permission denied
find: '/proc/9/task/235/fdinfo': Permission denied
find: '/proc/9/task/236/fdinfo': Permission denied
find: '/proc/9/task/237/fdinfo': Permission denied
find: '/proc/9/task/238/fdinfo': Permission denied
find: '/proc/9/task/239/fdinfo': Permission denied
find: '/proc/9/task/240/fdinfo': Permission denied
find: '/proc/9/task/241/fdinfo': Permission denied
find: '/proc/9/task/242/fdinfo': Permission denied
find: '/proc/9/task/243/fdinfo': Permission denied
find: '/proc/9/task/244/fdinfo': Permission denied
find: '/proc/9/task/245/fdinfo': Permission denied
find: '/proc/9/task/246/fdinfo': Permission denied
find: '/proc/9/task/247/fdinfo': Permission denied
find: '/proc/9/task/248/fdinfo': Permission denied
find: '/proc/9/task/249/fdinfo': Permission denied
find: '/proc/9/task/250/fdinfo': Permission denied
find: '/proc/9/task/251/fdinfo': Permission denied
find: '/proc/9/task/252/fdinfo': Permission denied
find: '/proc/9/task/253/fdinfo': Permission denied
find: '/proc/9/map_files': Permission denied
find: '/proc/9/fdinfo': Permission denied
dmesg: read kernel buffer failed: Operation not permitted
timeout: failed to run command 'journalctl': No such file or directory
timeout: failed to run command 'journalctl': No such file or directory
Thu Feb 29 17:49:13 UTC 2024 Capturing program information
Dump already generated: /var/opt/mssql/log/core.sqlservr.2_29_2024_17_46_25.9, moving to /var/opt/mssql/log/core.sqlservr.9.temp/core.sqlservr.9.gdmp
Moving logs to /var/opt/mssql/log/core.sqlservr.9.temp/log/paldumper-debug.log
Thu Feb 29 17:49:13 UTC 2024 Capturing program binaries
Thu Feb 29 17:49:14 UTC 2024 Not compressing the dump files, moving instead to: /var/opt/mssql/log/core.sqlservr.02_29_2024_17_46_26.9.d

And the container exits

Keep in mind that this specific container image and run command worked perfectly when Docker desktop Did work.

Am I missing something?

I’m not sure about it now, but I would suggest creating a new topic for it. Otherwise no one will read it who don’t know Docker Desktop. If you edit your post removing the MSSQL part, the discussion will not start in two topics even if someone finds this topic.

I’m just running through a lot of questions, but if you can create a new topic, I will think about the issue again. Unless someone else answers it before that.

1 Like