MrMeeb/cronicle-docker
1
0
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases 6 Wiki Activity

Container sometimes crashes when trying to own files that are read-only #9

New Issue
Closed
opened 2023-08-02 15:10:48 +00:00 by MrMeeb · 1 comment
MrMeeb commented 2023-08-02 15:10:48 +00:00
Owner
Copy Link

If mounting read-only volumes (e.g for certificates created by another container), sometimes it seems that cronicle will crash while trying to interact with them (while doing the permission check). Recreating the container normally resolves it

If mounting read-only volumes (e.g for certificates created by another container), sometimes it seems that cronicle will crash while trying to interact with them (while doing the permission check). Recreating the container normally resolves it
MrMeeb self-assigned this 2023-08-02 15:10:48 +00:00
MrMeeb commented 2023-08-02 15:45:36 +00:00
Author
Owner
Copy Link

Log excerpt:

cronicle-worker  | Checking permissions in /config and /app.
cronicle-worker  | Fixing permissions for /app (this can take some time).
cronicle-worker  | Fixing permissions for /config (this can take some time).
cronicle-worker  | chown: /config/keys/mm-oci-1/privkey.pem: Read-only file system
cronicle-worker  | chown: /config/keys/mm-oci-1/fullchain.pem: Read-only file system
cronicle-worker  | s6-rc: warning: unable to start service container-init: command exited 1
cronicle-worker  | /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
cronicle-worker  | /run/s6/basedir/scripts/rc.init: fatal: stopping the container.
cronicle-worker exited with code 0
Log excerpt: ``` cronicle-worker | Checking permissions in /config and /app. cronicle-worker | Fixing permissions for /app (this can take some time). cronicle-worker | Fixing permissions for /config (this can take some time). cronicle-worker | chown: /config/keys/mm-oci-1/privkey.pem: Read-only file system cronicle-worker | chown: /config/keys/mm-oci-1/fullchain.pem: Read-only file system cronicle-worker | s6-rc: warning: unable to start service container-init: command exited 1 cronicle-worker | /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information. cronicle-worker | /run/s6/basedir/scripts/rc.init: fatal: stopping the container. cronicle-worker exited with code 0 ```
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
MrMeeb
No Assignees MrMeeb
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MrMeeb/cronicle-docker#9
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?