Troubleshoot: Docker Error allocating lock for new volume: allocation failed; exceeded num_locks (2048)

Services Support
1

Hello,

My server pure services aren’t running. Using the local IP address in the browser I can see this error info:

StartOS - Diagnostic Mode

StartOS launch error:

Docker ErrorError: creating named volume "d22f2c60f2cab1ff3318f6da8ddbdecb60cb311d6f245b037fe4c84448193975": allocating lock for new volume: allocation failed; exceeded num_locks (2048)

Possible solutions:

Please contact support.

Clicking into the logs gives this detail:

024-10-20T07:27:56-05:00 2024-10-20T12:27:56.390753Z  INFO inner_main:setup_or_init:init: startos::init: Mounted Logs
2024-10-20T07:27:56-05:00 2024-10-20T12:27:56.436905Z  INFO inner_main:setup_or_init:init:bind: startos::disk::mount::util: Binding /embassy-data/package-data/tmp/var to /var/tmp
2024-10-20T07:27:56-05:00 2024-10-20T12:27:56.439796Z  INFO inner_main:setup_or_init:init:bind: startos::disk::mount::util: Binding /embassy-data/package-data/tmp/podman to /var/lib/containers
2024-10-20T07:27:56-05:00 2024-10-20T12:27:56.442126Z  INFO inner_main:setup_or_init:init: startos::init: Mounted Docker Data
2024-10-20T07:27:58-05:00 2024-10-20T12:27:58.206995Z  INFO inner_main:setup_or_init:init: startos::init: Enabling Docker QEMU Emulation
2024-10-20T07:27:58-05:00 2024-10-20T12:27:58.283723Z ERROR inner_main: startos::bins::start_init: Error: creating named volume "d22f2c60f2cab1ff3318f6da8ddbdecb60cb311d6f245b037fe4c84448193975": allocating lock for new volume: allocation failed; exceeded num_locks (2048)
2024-10-20T07:27:58-05:00 2024-10-20T12:27:58.283755Z DEBUG inner_main: startos::bins::start_init: Error: creating named volume "d22f2c60f2cab1ff3318f6da8ddbdecb60cb311d6f245b037fe4c84448193975": allocating lock for new volume: allocation failed; exceeded num_locks (2048)
2024-10-20T07:28:01-05:00 2024-10-20T12:28:01.080593Z ERROR inner_main:init: startos::context::diagnostic: Error: Docker Error: Error: creating named volume "d22f2c60f2cab1ff3318f6da8ddbdecb60cb311d6f245b037fe4c84448193975": allocating lock for new volume: allocation failed; exceeded num_locks (2048)
2024-10-20T07:28:01-05:00 : Starting diagnostic UI
2024-10-20T07:28:01-05:00 2024-10-20T12:28:01.080682Z DEBUG inner_main:init: startos::context::diagnostic: Error { source:
2024-10-20T07:28:01-05:00 0: Error: creating named volume "d22f2c60f2cab1ff3318f6da8ddbdecb60cb311d6f245b037fe4c84448193975": allocating lock for new volume: allocation failed; exceeded num_locks (2048)
2024-10-20T07:28:01-05:00 0: 
2024-10-20T07:28:01-05:00 Location:
2024-10-20T07:28:01-05:00 startos/src/util/mod.rs:163
2024-10-20T07:28:01-05:00 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ SPANTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
2024-10-20T07:28:01-05:00 0: startos::init::init
2024-10-20T07:28:01-05:00 at startos/src/init.rs:192
2024-10-20T07:28:01-05:00 1: startos::bins::start_init::setup_or_init
2024-10-20T07:28:01-05:00 at startos/src/bins/start_init.rs:23
2024-10-20T07:28:01-05:00 2: startos::bins::start_init::inner_main
2024-10-20T07:28:01-05:00 at startos/src/bins/start_init.rs:198
2024-10-20T07:28:01-05:00 Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
2024-10-20T07:28:01-05:00 Run with RUST_BACKTRACE=full to include source snippets., kind: Docker, revision: None }

Ideas?

2

You’re not able to start your Docker s. There are a couple of reasons why this might be, one that comes to mind is being out of disk space.

What services are you running? Are you running anything where you’ve been uploading many large files?

Did you complete this initial setup process all the way to the SSH stage? Do you have that set up? (see: Start9 | Using SSH)

3

Hello, Thanks and sorry it took me so long to get back to this. Yes, I did set it up and I am ssh’d in now as the start9 user.

What next?

In case you need general disk space output, here’s something:

start9@start:~$ df
Filesystem                                                                             1K-blocks       Used  Available Use% Mounted on
udev                                                                                    16345528          0   16345528   0% /dev
tmpfs                                                                                    3273840       1096    3272744   1% /run
overlay                                                                                 16369184      30880   16338304   1% /
/dev/nvme0n1p3                                                                          15728640    3309932   11999956  22% /media/embassy/next
tmpfs                                                                                   16369184         84   16369100   1% /dev/shm
tmpfs                                                                                       5120          0       5120   0% /run/lock
/dev/nvme0n1p2                                                                           1046512      60052     986460   6% /boot
tmpfs                                                                                    3273836          0    3273836   0% /run/user/1001
/dev/mapper/EMBASSY_BGOCZYMZUGFQHI7JQWBRNNCC5BM6PEL2RKGKJ3VMQC6B2RWLJJXA_main            8372224    1183484    6656068  16% /embassy-data/main
/dev/mapper/EMBASSY_BGOCZYMZUGFQHI7JQWBRNNCC5BM6PEL2RKGKJ3VMQC6B2RWLJJXA_package-data 3881730048 1236262440 2645271256  32% /embassy-data/package-data
tmpfs                                                                                    3273836          0    3273836   0% /run/user/1000

And these are the services I’ve been playing with:

image
image2754×1084 132 KB

Yes, I’ve added some large files for video serving, 2-4 LLMs for FreeGPT-2, and Bitcoin takes up quite a bit I think.

4

I did some digging of my own and found this:
https://github.com/containers/podman/issues/14195

I gathered some information without doing anything destructive:

start9@start:~$ sudo podman version
Client:       Podman Engine
Version:      4.5.1
API Version:  4.5.1
Go Version:   go1.19.8
Built:        Thu Jan  1 00:00:00 1970
OS/Arch:      linux/amd64
start9@start:~$ sudo podman ps -a
CONTAINER ID  IMAGE                                      COMMAND         CREATED      STATUS      PORTS       NAMES
34b4519aab14  docker.io/start9/filebrowser/main:2.27.0                   4 weeks ago  Created                 filebrowser.embassy
0b8a6a26f2ae  docker.io/start9/nextcloud/main:27.1.7                     4 weeks ago  Created                 nextcloud.embassy
76e1f264ba97  docker.io/start9/searxng/main:2024.7.20                    4 weeks ago  Created                 searxng.embassy
1305795a2877  docker.io/start9/bitcoind/main:27.1.0                      4 weeks ago  Created                 bitcoind.embassy
84cbb7301d01  docker.io/start9/jellyfin/main:10.9.7                      4 weeks ago  Created                 jellyfin.embassy
283089c5c454  docker.io/start9/mempool/main:2.5.1.2                      4 weeks ago  Created                 mempool.embassy
2707deaf4597  docker.io/start9/electrs/main:0.10.5                       4 weeks ago  Created                 electrs.embassy
820d212871e5  docker.io/start9/free-gpt/main:2.208.0310                  4 weeks ago  Created                 free-gpt.embassy
2eb146c96859  docker.io/start9/x_system/utils:latest     sleep infinity  2 weeks ago  Up 2 weeks              netdummy
start9@start:~$ sudo podman volume ls | wc -l
2039
start9@start:~$

I’m curious if you think I should prune the volumes (e.g. sudo podman volume prune).

I await your next suggestion.

5

I’m not clear on what might have caused this… maybe installing and uninstalling Services in quick succession?

Does your StartOS diagnostic screen offer you a System Rebuild button?

6

It does. I’ll try that and report back on the outcome.

7

That fixed it, thanks