dependency failed to start: container netbox-docker-netbox-1 exited (127)

[Juganooo]

Current Behavior

I tried to install netbox, docker compose up -d and get this error

docker compose up -d
[+] Running 4/6
 ✔ Container netbox-docker-redis-1                Running                                                                                                                                                0.0s 
 ✔ Container netbox-docker-redis-cache-1          Running                                                                                                                                                0.0s 
 ✔ Container netbox-docker-postgres-1             Running                                                                                                                                                0.0s 
 ✘ Container netbox-docker-netbox-1               Error                                                                                                                                                  1.3s 
 ⠹ Container netbox-docker-netbox-housekeeping-1  Recreated                                                                                                                                              1.2s 
 ⠹ Container netbox-docker-netbox-worker-1        Recreated                                                                                                                                              1.2s 
dependency failed to start: container netbox-docker-netbox-1 exited (127)
```

### Expected Behavior

docker compose up -d
[+] Running 6/6
 ✔ Container netbox-docker-redis-1                Running                                                                                                                                                0.0s 
 ✔ Container netbox-docker-redis-cache-1          Running                                                                                                                                                0.0s 
 ✔ Container netbox-docker-postgres-1             Running                                                                                                                                                0.0s 
 ✔ Container netbox-docker-netbox-1               Running                                                                                                                                                1.3s 
 ✔ Container netbox-docker-netbox-housekeeping-1  Running                                                                                                                                                1.2s 
 ✔ Container netbox-docker-netbox-worker-1        Running                                                                                                                                                1.2s 
```

### Docker Compose Version

Docker Compose version v2.24.5

### Docker Version

```text
Client: Docker Engine - Community
 Version:           25.0.3
 API version:       1.44
 Go version:        go1.21.6
 Git commit:        4debf41
 Built:             Tue Feb  6 21:14:26 2024
 OS/Arch:           linux/amd64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          25.0.3
  API version:      1.44 (minimum version 1.24)
  Go version:       go1.21.6
  Git commit:       f417435
  Built:            Tue Feb  6 21:14:26 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.28
  GitCommit:        ae07eda36dd25f8a1b98dfbf587313b99c0190bb
 runc:
  Version:          1.1.12
  GitCommit:        v1.1.12-0-g51d5e94
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0
```


### The git Revision

f1ca9ab7ebc16b288fd9da8825176c75d6b7ea4f

### The git Status

```text
Sur la branche release
Votre branche est à jour avec 'origin/release'.

rien à valider, la copie de travail est propre

On the release branch Your branch is up to date with 'origin/release'.

nothing to validate, the working copy is clean
```


### Startup Command

docker compose up -d

### NetBox Logs

```text
netbox-1  | /usr/bin/tini: error while loading shared libraries: libc.so.6: cannot open shared object file: Permission denied
```


### Content of docker-compose.override.yml

```yaml
version: '3.4'
services:
  netbox:
    ports:
      - "7000:8080"
    # If you want the Nginx unit status page visible from the
    # outside of the container add the following port mapping:
    # - "8001:8081"
    # healthcheck:
      # Time for which the health check can fail after the container is started.
      # This depends mostly on the performance of your database. On the first start,
      # when all tables need to be created the start_period should be higher than on
      # subsequent starts. For the first start after major version upgrades of NetBox
      # the start_period might also need to be set higher.
      # Default value in our docker-compose.yml is 60s
      # start_period: 90s
    environment:
      SKIP_SUPERUSER: "false"
      # SUPERUSER_API_TOKEN: ""
      # SUPERUSER_EMAIL: ""
      SUPERUSER_NAME: "admin"
      SUPERUSER_PASSWORD: "admin"
```

[Juganooo]

Maybe relevant to add
Linux openmielovault 6.1.0-0.deb11.7-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.20-2~bpo11+1 (2023-04-23) x86_64 GNU/Linux

[igrokit]

I have the same issue. Have you found a solution?

[sKuhLight]

If you're using a custom data-root (Docker root directory), permission handling for named volumes can sometimes get tricky — especially when the application inside the container runs as a non-root user.

What happens in this case is that the user inside the container (for example unit, UID 999) doesn't have access to its own files stored under the overlay2 directory on the host.
This can cause startup issues like missing shared libraries (libc.so.6 not found) or permission errors when the container tries to read its own filesystem layers.

---

You have two options:

Grant permissions for the entire Docker root directory

(simplest and ensures all containers with the same UID will work)

sudo setfacl -Rm u:999:rwx /path/to/docker-root
sudo setfacl -dRm u:999:rwx /path/to/docker-root

These commands add (not overwrite) ACLs for UID 999 recursively and set default ACLs for newly created volumes.

Or give explicit permissions to a specific container’s overlay layer

You can locate the container’s writable overlay2 directory with:

docker inspect $(docker ps -qf name=netbox-1) | grep UpperDir | cut -d'"' -f4

Replace name=netbox-1 as needed

Example output:

/media/docker/docker/overlay2/8cb6c2ef1d3b46e4b30b9e1e85c7a8db9dbf2e7e0d3cc35d611f1b2298b1ce12/diff

Then you can adjust permissions directly for that path e.g. /media/docker/docker/overlay2/8cb6c2ef1d3b46e4b30b9e1e85c7a8db9dbf2e7e0d3cc35d611f1b2298b1ce12

   sudo setfacl -Rm u:999:rwx /media/docker/docker/overlay2/8cb6c2ef1d3b46e4b30b9e1e85c7a8db9dbf2e7e0d3cc35d611f1b2298b1ce12
   sudo setfacl -dRm u:999:rwx /media/docker/docker/overlay2/8cb6c2ef1d3b46e4b30b9e1e85c7a8db9dbf2e7e0d3cc35d611f1b2298b1ce12