FS#72348 - [archboot] cannot properly create container due to pacman keyring not initiated

Attached to Project: Arch Linux
Opened by Xuanrui Qi (xuanrui) - Tuesday, 05 October 2021, 02:01 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 06 October 2021, 09:21 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

trying to create a container (# archboot-create-container.sh container) gives me the following errors:

error: config file /etc/pacman.d/mirrorlist could not be read: No such file or directory
error parsing '/etc/pacman.conf'
==> ERROR: You do not have sufficient permissions to read the pacman keyring.
==> Use 'pacman-key --init' to correct the keyring permissions.
Container container failed with error code 1.
Spawning container container on /home/xuanrui/archboot/container.
Press ^] three times within 1s to kill container.
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
warning: linux-5.14.8.arch1-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) linux-5.14.8.arch1-1

Total Installed Size: 131.22 MiB
Net Upgrade Size: 0.00 MiB

:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring [########################################] 100%
warning: Public keyring not found; have you run 'pacman-key --init'?
downloading required keys...
error: keyring is not writable
error: required key missing from keyring
error: failed to commit transaction (could not find or read file)
Errors occurred, no packages were upgraded.

Container container failed with error code 1.

Steps to reproduce:
Try to create a container using archboot-create-container.sh
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Wednesday, 06 October 2021, 09:21 GMT
Reason for closing:  Fixed
Additional comments about closing:  2021.10-8
Comment by Tobias Powalowski (tpowa) - Wednesday, 06 October 2021, 08:40 GMT
Which version do you use?
Comment by Xuanrui Qi (xuanrui) - Wednesday, 06 October 2021, 08:42 GMT
Actually, the latest update (10-8) seems to have fixed the issue.
THis issue can be closed. I guess the fix is somewhere between 3 and 8.
Comment by Tobias Powalowski (tpowa) - Wednesday, 06 October 2021, 09:20 GMT
Yes did a lot of changes yesterday, now all should work with 2021.10-8.

Loading...