Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

lockfile issue in '00-packages' after stage 3 #191

Closed
Babbleshack opened this issue Jun 7, 2018 · 3 comments
Closed

lockfile issue in '00-packages' after stage 3 #191

Babbleshack opened this issue Jun 7, 2018 · 3 comments

Comments

@Babbleshack
Copy link

Babbleshack commented Jun 7, 2018

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.

@Babbleshack Babbleshack changed the title Lockfile issue after stage 3 lockfile issue in '00-packages' after stage 3 Jun 7, 2018
@XECDesign
Copy link
Member

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.

@Babbleshack
Copy link
Author

That doesnt seem to be the case. This will happen even when continuing a successful build.

@XECDesign
Copy link
Member

XECDesign commented Jun 13, 2018

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants