You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CONTINUE=1 PRESERVE_CONTAINER=1 ./docker-build.sh has started failing on the package stage, with error:
[21:12:30] End /pi-gen/stage3/00-install-packages/01-run.sh
[21:12:30] End /pi-gen/stage3/00-install-packages
[21:12:30] Begin /pi-gen/stage3/01-tweaks
[21:12:30] Begin /pi-gen/stage3/01-tweaks/00-run.sh
[21:12:30] End /pi-gen/stage3/01-tweaks/00-run.sh
[21:12:30] End /pi-gen/stage3/01-tweaks
[21:12:30] End /pi-gen/stage3
[21:12:30] Begin /pi-gen/stage4
[21:12:30] Begin /pi-gen/stage4/prerun.sh
[21:12:30] End /pi-gen/stage4/prerun.sh
[21:12:30] Begin /pi-gen/stage4/00-enable-ssh
[21:12:30] Begin /pi-gen/stage4/00-enable-ssh/00-packages
E: Could not open lock file /var/lib/dpkg/lock - open (2: No such file or directory)
E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?
I have removed the export files from stage3.
I have tried to remove my 00-enable-ssh substage, however the issue is propagated.
The text was updated successfully, but these errors were encountered:
Babbleshack
changed the title
Lockfile issue after stage 3
lockfile issue in '00-packages' after stage 3
Jun 7, 2018
I think that would only happen if you're running two instanced of pi-gen at the same time, using the same files, or if you are continuing a build which was killed while dpkg was running.
In that case, could you make sure everything is unmounted, then build the full stock image from scratch and post the log (something like sudo ./build.sh |& tee build.log would work)?
EDIT: Either without using Docker or making sure you have a new unused container.
CONTINUE=1 PRESERVE_CONTAINER=1 ./docker-build.sh
has started failing on the package stage, with error:I have removed the export files from
stage3
.I have tried to remove my
00-enable-ssh
substage, however the issue is propagated.The text was updated successfully, but these errors were encountered: