Skip to content

can't install packages when using proot  #331

Open
@LukeLabrie

Description

@LukeLabrie

I am running junest in a manjarolinux/base docker container based on this image. When I try to run junest I get the following error

getent command failed or does not exist. Binding directly from /etc/passwd.
bwrap: No permissions to creating new namespace, likely because the kernel does not allow non-privileged user namespaces. On e.g. debian this can be enabled with 'sysctl kernel.unprivileged_userns_clone=1'.
Error: Something went wrong while executing bwrap command. Exiting
/home/myuser/junest/lib/core/wrappers.sh: line 25: mkdir: No such file or directory

after reading this issue I try running junest proot -f, I no longer get the above error, but when I try to install packages with yay, for instance yay -S openmc-git, I get the following error

 -> error fetching openmc-git:  
	 context: exec: "systemd-run": executable file not found in $PATH
error fetching nuclear-data:  
	 context: exec: "systemd-run": executable file not found in $PATH
error fetching python-cad_to_openmc:  
	 context: exec: "systemd-run": executable file not found in $PATH
error fetching moab:  
	 context: exec: "systemd-run": executable file not found in $PATH
error fetching dagmc-git:  
	 context: exec: "systemd-run": executable file not found in $PATH
error fetching double-down-git:  
	 context: exec: "systemd-run": executable file not found in $PATH

I tried sudo find / -name systemd-run and it was nowhere to be found. Does proot not have the systemd executables? I have a feeling it might have something to do with running in a docker container. I've done that before without issue, but now I am using a different computer.

Any ideas?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions