Have apt-get wait for a lock rather than erroring #167
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Per the suggestion in this article (https://blog.sinjakli.co.uk/2021/10/25/waiting-for-apt-locks-without-the-hacky-bash-scripts/), this setting tells apt-get to wait for the package lock. Our packer builds have been breaking because this script is conflicting with some internal ubuntu update process which is also using apt-get. We recently updated all out internal scripts to use this setting, and we were able to get around the issue. However, this digitalocean provided script is still erroring.
According to that article, the two options are either:
DPkg::Lock::Timeout
value to a reasonable timeout.apt
, which automatically sets this value. However,apt
comes with the following warning:WARNING : apt does not have a stable CLI interface. Use with caution in scripts.
The former seemed more robust, so it's what we used, and what I would recommend using here.