-
Notifications
You must be signed in to change notification settings - Fork 3
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
/var/log/socklog/cron: Permission denied #2
Comments
So it turns out that the problem is that the fix-attrs.d file that socklog uses wants to set the user to nobody:nogroup, which somehow fails. As a result, the numerical fallback ids are used which do not represent any actual user in my container. |
Can you post your full Dockerfile? I'm unable to reproduce. I used: FROM ubuntu:16.04
# Install s6-overlay
ADD https://github.com/just-containers/s6-overlay/releases/download/v1.21.2.2/s6-overlay-amd64.tar.gz /tmp/
RUN tar xzf /tmp/s6-overlay-amd64.tar.gz -C /
# Install socklog-overlay
ADD https://github.com/just-containers/socklog-overlay/releases/download/v2.1.0-0/socklog-overlay-amd64.tar.gz /tmp/
RUN tar xzf /tmp/socklog-overlay-amd64.tar.gz -C /
RUN apt-get update && \
apt-get install -y cron
COPY root /
ENTRYPOINT ["/init"] Then under #!/usr/bin/with-contenv sh
exec cron -f And everything is working fine. |
I was using an old version of s6-overlay, which exhibited the fix-attrs issue I mentioned above. Upgrading fixed it, sorry for the bother. |
I added this to a Dockerfile along with s6-overlay. I want to see the log output of cron without installing rsyslog proper.
After I start my container, I see repeatedly this message in the docker logs:
s6-log: fatal: unable to mkdir /var/log/socklog/cron: Permission denied
Container is ubuntu:16:04.
The text was updated successfully, but these errors were encountered: