-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Podman Rootless Container Issue - failed to write to /proc/self/oom_score_adj: Permission denied #2961
Comments
Uhm, the error message is totally misleading when using Mosquitto 2.x. Looking at the contents of
My mosquitto.conf
And my podman / Docker compose.yml file is
Am I using an unsupported cypher / library ? Is the openssl version I used too recent for Mosquitto ?
|
It's also generating this error during certificate creation
And server.crt is empty 😢. I tried to generate it using
Legacy procider should've make it work. I also added |
Actually the issue might be related to the "-nodes" option I used here (in some cases it's required, otherwise the prompt Updated to this generates the server.crt certificate correctly
Onto the next error
Probably some permission errors. But what worries me is the last line
|
Now it works but I do not know why ... I regenerated all certificates, keys and CA ... Then from outside the container I did
And now it seems to work
|
I am getting an error
When trying to run the latest image of eclipse-mosquitto (e.g. from docker.io).
I originally thought this was a podman bug -> containers/podman#20886
However, after playing around a bit with mosquitto and trying to build using the Dockerfile, maybe the issue is within eclipse-mosquitto itself.
I tried to build using the following command
I tried:
[conmon:d]: failed to write to /proc/self/oom_score_adj: Permission denied
[conmon:d]: failed to write to /proc/self/oom_score_adj: Permission denied
I tried a quick diff between the 2.0-openssl and 1.6-openssl Dockerfile
There doesn't seem to be a whole lot of differences. Any idea what could be causing the error ?
The text was updated successfully, but these errors were encountered: