Solved /proc/ is not mounted error when I try to chroot ubuntu 23.10 installed inside the Linuxulator...

I know this old thread but my problem is connected to: So after ubuntu lts 24 upgrade I tried tricks above and got rid from systemd errors, but reached standstill of pulseaudio; be more detailed it's service share works inside chroot only, and need manually intervene to point to socket everytime.. Also is there a non-systemd ubuntu distribution?

 
You want to use Rocky Linux because it doesnt have the systemd issues that Ubuntu has

I would also recommend using Rocky Linux Podman containers or a Rocky Linux jail
instead of using a chroot

This is my freebsd-cuda project that enables Cuda on using Rocky Linux Podman containers
which has a pulseaudio socket for apps that need it


This is the nix package manager in a Podman container
( which doesnt have cuda support )


Here is Davinci Resolve running in a Rocky Linux Jail with pulseaudio


If you have a look through those projects you should get the idea

Forget about Ubuntu on Freebsd using a chroot, jail or podman container
you will just get lots of systemd errors

You want to set up Rocky Linux as the default for the Linuxulator
then use Rocky Linux Podman containers and they work perfectly together that my advice
I don't use chroot, I complain about pulseaduio no more auto connect like before (works only inside chroot sessions). also forgot to mention, I can't use rocky linux nor debian; need specific packages available for ubuntu.
 
I can't use rocky linux nor debian; need specific packages available for ubuntu.
What packages? Backports?

You shouldn't need any particular distro's packages unless you're dealing with some real hot garbage. Even then you should be easily able to extract what is within the packages and get them running on another distro. Assuming the whole "Don't break userspace" promise on the Linux side still holds true.

But here is the thing about that promise: They never promised userspace wouldn't break userspace and lately a certain piece of cancer running as PID1 everywhere in the Linux world has been hell bent on doing that. So maybe you need a bunch of shims to make it work on an actual Linux distro and not what is basically Fedora with a skin on it like modern Ubuntu and pretty much everything else from ArchLinux to Gentoo is.

It's only going to get worse in the near future. We have a about 1 year on the current LTS linux kernel which is the last real release in my opinion. Since the LKML just changed some major rules and dropped lots of hardware support/drivers. Which are now marked "abandoned" and "possible security exploit because some AI said it might be and no one bothered to check for real". They're "abandoned" because all the Russians and other people unlucky enough to be born in the wrong country who were removed from contributing for no other reason than Linus doesn't want to lose his DoD paycheck were the people that were maintaining them. By old hardware I mean a lot of stuff released between 1999-2015 by the way. Even freakin' drivers for old mice were yanked out in the latest merge window.

Oh and now they're letting anyone submit code generated with AI who are no longer being required to tag it as so. They voted to remove that rule in the last few weeks. Even Linus submitted a new large diff generated fully with AI. Along with all the documentation and even the emails he sent to the mailing lists about it. Real expert engineering happening over there wouldn't you agree?

Save yourself the headache and 1) Use a different distro for your linuxemu/VM needs and 2) Figure out some other way to get the userspace software you need (I suggest building it from source code).
 
Back
Top