sameersbn / sameersbn/docker-gitlab
Restarting GitLab fails with "sudu:unable to send audit message"
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Did a weekly update to fedora 33 with dnf and GitLab startup stops with:
[server189 ~]$ docker run --detach=true --name=gitlab --hostname=server189 --publish=10022:22 --publish=10443:443 --env-file=/etc/podman/gitlab.conf -v /var/lib/containers/volumes/gitlab/data:/home/git/data docker.io/sameersbn/gitlab
Loading /etc/docker-gitlab/runtime/env-defaults
Initializing logdir...
Initializing datadir...
sudo: unable to send audit message
sudo: pam_open_session: System error
sudo: policy plugin failed session initialization
Any ideas on what to investigate would be greatly appreciated!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported docker run command after the Fedora 33 update and inspect the container startup output around the sudo and PAM errors. The issue names no repository file or test; done would require identifying the cause of the startup failure and documenting a verified resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, fedora
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100