FS#61043 - [pacstrap] pacstrap -c -d $dir base command fails executing

Attached to Project: Arch Linux
Opened by Jelle van der Waa (jelly) - Wednesday, 12 December 2018, 10:51 GMT
Last edited by Jelle van der Waa (jelly) - Saturday, 22 July 2023, 13:47 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jelle van der Waa (jelly)
Levente Polyak (anthraxx)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:


Additional info:
( 8/13) Creating system user accounts...
( 9/13) Creating temporary files...
error: command failed to execute correctly
(10/13) Reloading device manager configuration...
Skipped: Device manager is not running.
(11/13) Arming ConditionNeedsUpdate...
(12/13) Updating the info directory file...


Steps to reproduce:

pacstrap -c -d foo base


This task depends upon

Closed by  Jelle van der Waa (jelly)
Saturday, 22 July 2023, 13:47 GMT
Reason for closing:  Upstream
Comment by Conrad Hoffmann (conrausch) - Tuesday, 08 September 2020, 20:05 GMT
I think this might be systemd having issues with your permissions. When reproducing this, I actually get this:

( 6/11) Creating temporary files...
Detected unsafe path transition / → /etc during canonicalization of /etc.
<many more of those>
error: command failed to execute correctly
( 7/11) Reloading device manager configuration...

As pointed out in this Github issue: https://github.com/systemd/systemd/issues/11282#issuecomment-450347268 this is probably an issue with permissions.

I can reproduce the error when I run `sudo pacstrap -c -d foo base` where `foo` is a directory owned by my regular user. If i create it with `sudo mkdir foo` and then run `sudo pacstrap -c -d foo base` then systemd is happy and all is well.

Can you confirm? If so, I think this bug could be closed? Or should pacstrap be printing a warning in this case?
Comment by Jelle van der Waa (jelly) - Saturday, 22 July 2023, 13:46 GMT

Loading...