Skip to content

[Error] Pacman "call to execv failed" on a fresh Arch container #1602

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

Closed
nfp0 opened this issue Nov 4, 2024 · 3 comments
Closed

[Error] Pacman "call to execv failed" on a fresh Arch container #1602

nfp0 opened this issue Nov 4, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@nfp0
Copy link

nfp0 commented Nov 4, 2024

Describe the bug
On a fresh Arch container (on an Arch host), running something like sudo pacman -S nano to install nano outputs the following error:

:: Running pre-transaction hooks...
(1/1) Distrobox hook /etc/distrobox-pre-hook.sh...
call to execv failed (No such file or directory)
error: command failed to execute correctly

The application installs correctly, but I wonder what that error is.

To Reproduce

  1. Create an Arch box with something like distrobox create -n Arch -i archlinux
  2. Run sudo pacman -S nano after entering the container
  3. Observe the error.

Desktop

  • I am using Podman version 5.2.5 on Arch Linux.
  • Distrobox version 1.8.0 installed through the Arch repos.
@nfp0 nfp0 added the bug Something isn't working label Nov 4, 2024
@hexisXz
Copy link

hexisXz commented Nov 22, 2024

I have this same issue...

89luca89 added a commit that referenced this issue Dec 10, 2024
@kv7-coder
Copy link

I have this same issue...

I installed Arch in the following way:

distrobox create -i archlinux --name arch --hostname archlinux --home /home/$(whoami)/arch --root

2024-12-27_21-29

@twlswan
Copy link

twlswan commented Jan 5, 2025

I have this same issue...

I installed Arch in the following way:

distrobox create -i archlinux --name arch --hostname archlinux --home /home/$(whoami)/arch --root

2024-12-27_21-29

Me too but it's normal since the script installs only v1.8.0 from October. I guess I should've used the script that installed from the master branch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants