-
Notifications
You must be signed in to change notification settings - Fork 70
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
Unable to restart due elasticsearch-init
container
#212
Comments
will be fixed in: #215 |
monotek
pushed a commit
that referenced
this issue
Sep 26, 2023
monotek
added a commit
that referenced
this issue
Sep 26, 2023
* Fixes #212, fixes #200 - Switch to Zammad 6.1. * Solve #203 - attachment upload * set rofs to true again & fix tmp dir issues Signed-off-by: André Bauer <[email protected]> --------- Signed-off-by: André Bauer <[email protected]> Co-authored-by: André Bauer <[email protected]>
2 tasks
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After a cluster restart zammad is unable to restart, since the
elasticsearch-init
container does not complete without an error code. The logs [1] show an error associated with a read only file system (/opt/zammad/lib/static_assets.rb:177:in
initialize': Read-only file system @ rb_sysopen - /opt/zammad/public/assets/images/02be6b7d09f0d0eed30936e7b9ec676b.png (Errno::EROFS)). The manifest [2] does not list a mount for
/opt/zammad/public/`.[2]
The text was updated successfully, but these errors were encountered: