Open Voidthe opened 12 months ago
Upon review it was because I forgot to run podman system reset
Hi @Voidthe, I have same problem, it solved just when add --privileged when creating container, podman command will be like this : podman run --replace --privileged -it --entrypoint sh --name loki --publish 3020:3100 --volume /var/lib/containers/svc_podman/loki/config/:/etc/loki/:z,rw --env config.file=/etc/loki/local-config.yml --env log-config-reverse-order=true --env config.expand-env=true docker.io/grafana/loki:main
Describe the bug When attempting to sh into the container you will get an SELinux error If you
setenforce 0
then this issue is not present and the container will start regularlyTo Reproduce Steps to reproduce the behavior:
Expected behavior Get a shell inside the container
Environment:
Screenshots, Promtail config, or terminal output Podman command:
/usr/bin/podman run --replace -it --entrypoint sh --name loki --publish 3020:3100 --volume /var/lib/containers/svc_podman/loki/config/:/etc/loki/:z,rw --env config.file=/etc/loki/local-config.yml --env log-config-reverse-order=true --env config.expand-env=true docker.io/grafana/loki:main
Result:SELinux Error: