CI: mkosi-mainline: Workaround 'dpkg: error: dpkg frontend lock' #284
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.
Mkosi's own dracut hook, which is triggered from
dpkg -i
, callsdpkg-reconfigure
causing dpkg frontend lock conflict. Butinitrd.img
is generated correctly. Workaround by ignoringdpkg-reconfigure
errors in the hook.dpkg: error: dpkg frontend lock was locked by another process with pid 5
Note: removing the lock file is always wrong, can damage the locked area
and the entire system. See https://wiki.debian.org/Teams/Dpkg/FAQ#db-lock.
run-parts: /etc/kernel/postinst.d/zz-systemd-boot exited with return code 2
Link: #283
Description
I did not investigate thoroughly all internal workings of
dpkg -i
/dpkg-reconfigure
and what is changed since last week in Ubuntu (old action logs are not enough to clarify this.)How Has This Been Tested?
Locally.