I just upgraded my Pi (4) to the latest arch linux ARM (aarch64) and I'm getting the following error messages for ultrafeeder startup:
Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: chmod /dev/console: read-only file system: unknown
I'm using basically the docker compose setup from this repository.
If I comment out the line
volumes:
- /dev:/dev:ro
the container will start up, but won't find my rtlsdr device. I'm guessing something changed in the base Image you are using that now tries to chmod /dev/console which fails on RO filesystem, or a newer docker version is enforcing RO more strictly?
Is it really necessary to mount the whole /dev ?
Other containers start up fine on the host system. It's only ultrafeeder that fails currently.
Docker version:
Docker version 27.3.1, build ce1223035a
Docker Compose version 2.29.7
I just upgraded my Pi (4) to the latest arch linux ARM (aarch64) and I'm getting the following error messages for ultrafeeder startup:
I'm using basically the docker compose setup from this repository.
If I comment out the line
the container will start up, but won't find my rtlsdr device. I'm guessing something changed in the base Image you are using that now tries to chmod /dev/console which fails on RO filesystem, or a newer docker version is enforcing RO more strictly?
Is it really necessary to mount the whole
/dev
?Other containers start up fine on the host system. It's only ultrafeeder that fails currently.
Docker version: