Closed unlucio closed 2 years ago
Hi, at lease for me this is not the case. I already answered in the mentioned issue. Just re-tested docker exec gitlab update-permissions
without any problems. I've created a small Shell Script for start/stop. Please test again, and report back. otherwise I'll close this MR.
Closed, as I'm not able to reproduce and no response from the creator if the problem still exist.
If not privileged every container created from this image will keep crashing with the error:
sleep: cannot read realtime clock: Operation not permitted
This seems to be a known problem as found on https://gitlab.com/ulm0/gitlab/-/issues/14.
Unfortunately without the
--privileged
flag no amount ofdocker exec
will help to solve the problem as the container will either be dead (so not reachable viaexec
) or die right after it.