Skip to content
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

blue-build distroboxes are broken/bluebuild build podman errors #218

Closed
renner0e opened this issue Aug 17, 2024 · 4 comments
Closed

blue-build distroboxes are broken/bluebuild build podman errors #218

renner0e opened this issue Aug 17, 2024 · 4 comments

Comments

@renner0e
Copy link

[04:40:28 server:local-40] => time="2024-08-17T04:40:28+02:00" level=error msg="cannot find UID/GID for user user: no subuid ranges found for user \"user\" in /etc/subuid - check rootless mode in man pages."
[04:40:28 server:local-40] => time="2024-08-17T04:40:28+02:00" level=warning msg="Using rootless single mapping into the namespace. This might break some images. Check /etc/subuid and /etc/subgid for adding sub*ids if not using a network user"
[04:40:28 server:local-40] => time="2024-08-17T04:40:28+02:00" level=error msg="cannot find UID/GID for user user: no subuid ranges found for user \"user\" in /etc/subuid - check rootless mode in man pages."
[04:40:28 server:local-40] => time="2024-08-17T04:40:28+02:00" level=warning msg="Using rootless single mapping into the namespace. This might break some images. Check /etc/subuid and /etc/subgid for adding sub*ids if not using a network user"
[04:40:28 server:local-40] => time="2024-08-17T04:40:28+02:00" level=error msg="cannot find UID/GID for user user: no subuid ranges found for user \"user\" in /etc/subuid - check rootless mode in man pages."
[04:40:28 server:local-40] => time="2024-08-17T04:40:28+02:00" level=warning msg="Using rootless single mapping into the namespace. This might break some images. Check /etc/subuid and /etc/subgid for adding sub*ids if not using a network user"
[04:40:28 server:local-40] => time="2024-08-17T04:40:28+02:00" level=error msg="cannot find UID/GID for user user: no subuid ranges found for user \"user\" in /etc/subuid - check rootless mode in man pages."
[04:40:28 server:local-40] => time="2024-08-17T04:40:28+02:00" level=warning msg="Using rootless single mapping into the namespace. This might break some images. Check /etc/subuid and /etc/subgid for adding sub*ids if not using a network user"
[04:40:28 server:local-40] => time="2024-08-17T04:40:28+02:00" level=error msg="cannot find UID/GID for user user: no subuid ranges found for user \"user\" in /etc/subuid - check rootless mode in man pages."
[04:40:28 server:local-40] => time="2024-08-17T04:40:28+02:00" level=warning msg="Using rootless single mapping into the namespace. This might break some images. Check /etc/subuid and /etc/subgid for adding sub*ids if not using a network user"
[04:40:28 server:local-40] => time="2024-08-17T04:40:28+02:00" level=error msg="invalid internal status, try resetting the pause process with \"podman system migrate\": cannot re-exec process to join the existing user namespace

My podman installation works fine on aurora because distrobox works and hello world is also fine.
Something related to the distroboxes are broken, the exact same repo/template file works on the cargo install method.

I followed the exact steps that were in the README

distrobox create blue-build --image ghcr.io/blue-build/cli
distrobox enter blue-build
distrobox-export --bin $(which bluebuild --export-path ~/.local/bin/distrobox
exit
...

I layered zsh on my host and konsole executes zsh -l on startup if that matters for any reason.
BlueBuild 0.8.12

Am I missing something?

@gmpinder
Copy link
Member

Yeah we have an issue open to fix the distrobox setup. We had one of our users get it working. Here's their message in our Discord:

Sharing a working distrobox-assemble configuration for the cli. I've successfully used this with both bluebuild build and bluebuild switch. This method relies on the podman build driver. Haven't gotten the default (docker?) method working.

In distrobox.ini:

[bluebuild-root]
#image=ghcr.io/blue-build/cli:latest
image=ghcr.io/blue-build/cli:main
home="~/distrobox/bluebuild"
exported_bins="/usr/bin/bluebuild"
additional_packages=""
init_hooks="ln -sf /usr/bin/distrobox-host-exec /usr/local/bin/podman"
init_hooks="ln -sf /usr/bin/distrobox-host-exec /usr/local/bin/rpm-ostree"
init_hooks="ln -sf /usr/bin/distrobox-host-exec /usr/local/bin/ostree"
init=false
unshare_all=false
nvidia=false
pull=true
root=true
replace=true
start_now=true
exported_apps=""
volume="/etc/bluebuild:/etc/bluebuild:z"

In ~/.bashrc:

if [ -f "${HOME}/.local/bin/bluebuild" ]; then
  bluebuild() {
    local args=("$@")
    if (( ${#args[@]} > 0 )); then
      case "${args[0]}" in
        build|switch)
          ${HOME}/.local/bin/bluebuild "${args[0]}" --build-driver=podman "${args[@]:1}"
          ;;
        *)
          ${HOME}/.local/bin/bluebuild "$@"
          ;;
      esac
    else
      ${HOME}/.local/bin/bluebuild
    fi
  }
fi

@gmpinder
Copy link
Member

The in draft PR is #160, the original issue is #145

@sukarn-m
Copy link

Yeah we have an issue open to fix the distrobox setup. We had one of our users get it working. Here's their message in our Discord:

For what it's worth, I'm still happily using this configuration since I posted it on the discord.

Some of the steps in that distrobox-assemble configuration might be unnecessary, but I haven't bothered investigating whether it still works are removing some parts of it.

If this works for other people too, it might be worth temporarily putting this in the documentation until the underlying issue is resolved.

@gmpinder
Copy link
Member

Updated our README and included a distrobox.ini for use with distrobox assemble. We don't recommend trying to use this method to do local rebasing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants