-
-
Notifications
You must be signed in to change notification settings - Fork 280
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Main container will not start #438
Comments
Can you show the output of |
Certainly (no updates available) [bcrockett@docker51 ~]$ docker info |
Can you post full output please? Like:
|
sorry
|
Might be an issue with your host, this looks similar to #352 What's the output of the following commands?:
|
Seems like it works
|
Any update/resolution here? |
For some reason, mkdir cannot create crontabs dir, but any other dirname works fine.. Also if the "Backing Filesystem: zfs" is not zfs, then this problem goes away.. |
Support guidelines
I've found a bug and checked that ...
Description
[cont-init.d] 07-svc-cron.sh: executing...
mkdir: cannot create directory ‘/var/spool/cron/crontabs’: Invalid argument
[cont-init.d] 07-svc-cron.sh: exited 1.
Expected behaviour
starting
Actual behaviour
[cont-init.d] 07-svc-cron.sh: executing...
mkdir: cannot create directory ‘/var/spool/cron/crontabs’: Invalid argument
[cont-init.d] 07-svc-cron.sh: exited 1.
Steps to reproduce
docker run -d --restart=always 8070:8000 -v rse-librenms:/data -e TZ=America/New_York -e DB_HOST=192.168.1.51 -e DB_NAME=librenms -e DB_PASSWORD=X librenms/librenms:latest
Docker info
Docker Compose config
I don't use docker compose
Logs
Additional info
No response
The text was updated successfully, but these errors were encountered: