Skip to content
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

readonly /tmp #200

Closed
mkmik opened this issue Jul 25, 2019 · 0 comments · Fixed by #202
Closed

readonly /tmp #200

mkmik opened this issue Jul 25, 2019 · 0 comments · Fixed by #202
Assignees
Labels
Milestone

Comments

@mkmik
Copy link
Collaborator

mkmik commented Jul 25, 2019

klog (the glog fork used by kubernetes) commits suicide when trying to write an error

log: exiting because of error: log: cannot create log: open /tmp/controller.sealed-secrets-controller-665d687cc6-kjgl5.unknownuser.log.ERROR.20190725-153353.1: read-only file system
@mkmik mkmik added the bug label Jul 25, 2019
@mkmik mkmik self-assigned this Jul 25, 2019
mkmik pushed a commit that referenced this issue Jul 25, 2019
Our deployment template uses the `readOnlyRootFilesystem` but the k8s `klog` library
likes to write logs in `/tmp`.

Let's mount a writable `/tmp` dir.

Closes #200
@mkmik mkmik mentioned this issue Jul 25, 2019
mkmik pushed a commit that referenced this issue Jul 25, 2019
Our deployment template uses the `readOnlyRootFilesystem` but the k8s `klog` library
likes to write logs in `/tmp`.

Let's mount a writable `/tmp` dir.

Closes #200
bors bot added a commit that referenced this issue Jul 25, 2019
202: Writable /tmp r=mkmik a=mkmik

Our deployment template uses the `readOnlyRootFilesystem` but the k8s `klog` library
likes to write logs in `/tmp`.

Let's mount a writable `/tmp` dir.

Closes #200

Co-authored-by: Marko Mikulicic <mkm@bitnami.com>
@bors bors bot closed this as completed in #202 Jul 25, 2019
@mkmik mkmik added this to the v0.8.1 milestone Jul 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant