docker / docker/docker-install
Wait for dpgk lock to be released
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3.2k
- Forks
- 863
- Avg merge
- 3h 15m
- Merged PRs (30d)
- 2
Description
We get frequent errors when running the installation script in the context of build agents hosted on Azure DevOps
E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 5322 (apt)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
##[error]Bash exited with code '100'.
##[warning]RetryHelper encountered task failure, will retry (attempt #: 1 out of 3) after 1000 ms
apt-get supports adding a new parameter to wait for the lock to be released
apt-get update -o DPkg::Lock::Timeout=600 -qq
which would reduce the number of failures
Contributor guide
No contributing guide indexed for this repository
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
Inspect the installation script for its apt-get update invocation and compare it with the lock-timeout form shown in the issue. Run the script in an Azure DevOps build-agent context, or otherwise exercise the package-install path while apt holds the dpkg lock; done means the script waits for the lock instead of failing with exit code 100.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- devops, operating-systems
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100