Skip to content

Conversation

@thaJeztah
Copy link
Member

I saw Cirrus CI / Vagrant BOX:rockylinux/[email protected] failing during setting up Vagrant, which may be due to other scripts provisioning the machine;

Reading package lists...
apt-get install -y libvirt-daemon libvirt-daemon-system vagrant vagrant-libvirt
E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 2496 (apt-get)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?

Configure dpkg to wait for locks to be released instead of failing. I used 60 second as timeout, which is relatively long, but given that the Vagrant checks are known to take some time to run, is probably fine.

@thaJeztah
Copy link
Member Author

thaJeztah commented Jul 5, 2023

Hm... not supported?

apt-get DPkg::Lock::Timeout=60 update
E: Invalid operation DPkg::Lock::Timeout=60

Exit status: 100

edit: DOH! didn't add the -o 🤦

I saw Cirrus CI / Vagrant BOX:rockylinux/[email protected] failing during setting
up Vagrant, which may be due to other scripts provisioning the machine;

    Reading package lists...
    apt-get install -y libvirt-daemon libvirt-daemon-system vagrant vagrant-libvirt
    E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 2496 (apt-get)
    E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?

Configure dpkg to wait for locks to be released instead of failing. I used
60 second as timeout, which is relatively long, but given that the Vagrant
checks are known to take some time to run, is probably fine.

Signed-off-by: Sebastiaan van Stijn <[email protected]>
@thaJeztah
Copy link
Member Author

Should be fixed now

Copy link
Member

@fuweid fuweid left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@fuweid fuweid merged commit 9afa225 into containerd:main Jul 9, 2023
@thaJeztah thaJeztah deleted the vagrant_locking branch July 9, 2023 11:23
@thaJeztah thaJeztah added the cherry-picked/1.7.x PR commits are cherry-picked into release/1.7 branch label Jul 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cherry-picked/1.7.x PR commits are cherry-picked into release/1.7 branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants