There have been multiple accounts created with the sole purpose of posting advertisement posts or replies containing unsolicited advertising.

Accounts which solely post advertisements, or persistently post them may be terminated.

Running Arch in chroot

I am using Debian for long time and really like it for stability. Recently I wondered if it is possible to run Arch Linux from chroot. I want to run full Wayland session from Arch. I found Archbox project and it is worked for me, but I couldn’t start any Wayland compositor from tty (Error: can’t connect to Wayland socket . ). How can I properly do this? Or maybe there is a better way than chroot?

BaalInvoker ,

Why not use distrobox?

user_naa OP ,

I don’t think I can run native Wayland session from container

kolorafa ,

You can use wayland in container but the easy way probably would require to give whole GPU to the container (but my knowlwdge is limited)

What I do know that this project is doing that: games-on-whales.github.io

That also came up in search results that could help: unix.stackexchange.com/a/359244

user_naa OP ,

Why I need a full isolated container? Can’t I just use chroot?

seaQueue ,
@seaQueue@lemmy.world avatar

Because you’re relying on compatibility between older Debian software (systemd, etc) and newer versions installed in the chroot. Things get weird quickly.

Consider a nested privileged container instead (LXC or similar) and cross your fingers that Debian systemd and Arch systemd play nice.

If the above fails just make a VM and pass through the GPU with GVT-g (otherwise pass through the entire GPU.)

If all of that fails install Arch to a USB attached SSD or something.

user_naa OP ,

What Systemd compatibility I need to run Graphics session?

possiblylinux127 ,

You can

seaQueue ,
@seaQueue@lemmy.world avatar

If you’re using an Intel chip look into GVT-g and consider running Arch from a VM, that’ll be the closest thing to native.

The unfortunate thing about running an Arch container from a Debian host is that you’re relying on an older kernel and an older systemd host side and I’ve found that often causes compatibility problems inside the Arch container. If you are very, very lucky Arch will just work inside the container, but IME that’s fairly rare as systemd often has breaking changes over several releases (and Arch tends to be at least several releases ahead of Debian.)

user_naa OP ,

If you’re using an Intel chip look into GVT-g and consider running Arch from a VM, that’ll be the closest thing to native.

I want to start clear Arch Wayland session on one my ttys and want to Arch have full direct hardware access.

The unfortunate thing about running an Arch container from a Debian host is that you’re relying on an older kernel

I use latest Linux-libre on my Debian machine and everything works well.

If you are very, very lucky Arch will just work inside the container, but IME that’s fairly rare as systemd often has breaking changes over several releases (and Arch tends to be at least several releases ahead of Debian.)

As I mentioned earlier I tried running Archbox. It is basically script to easy set up chroot. The main problem was that compositor couldn’t connect to Wayland socket.

possiblylinux127 ,

Use distrobox with podman

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • [email protected]
  • random
  • lifeLocal
  • goranko
  • All magazines
    •