You are not logged in.
Pages: 1
I thought I would take lxc for a spin on an older desktop I'm using for server duties. I haven't tried lxc before but I had run kvm-qemu on this computer before, but it sounded relatively straight forward. : ( I have hit trouble with getting a container to start and have run out of google search idea's, so here is what I get:
$ lxc-start -F -n chimdev
lxc-start: chimdev: ../src/lxc/cgroups/cgfsng.c: initialize_cgroups: 3832 Cannot allocate memory - Failed to initialize cgroups
lxc-start: chimdev: ../src/lxc/cgroups/cgroup.c: cgroup_init: 34 Bad file descriptor - Failed to initialize cgroup driver
lxc-start: chimdev: ../src/lxc/start.c: lxc_init: 862 Failed to initialize cgroup driver
lxc-start: chimdev: ../src/lxc/start.c: __lxc_start: 2027 Failed to initialize container "chimdev"
lxc-start: chimdev: ../src/lxc/tools/lxc_start.c: main: 306 The container failed to start
lxc-start: chimdev: ../src/lxc/tools/lxc_start.c: main: 311 Additional information can be obtained by setting the --logpriority options "
If I use the lxc-unpriv-start command I get this:
$ lxc-unpriv-start -n chimdev
Can't start an unprivileged container on a pure CGroups v2 host without a systemd user session running.
If you are trying to get a non-interactive user to have unprivileged containers running, you need to
enable lingering sessions for that user, via loginctl enable-linger <user> as root.
Some more ideas to pursue would be appreciated as I said earlier I haven't tangled with containers before. Finding information on the subject when not using systemd is reasonably thin.
I had trouble with gdebi some time ago, they said they were fixing it. But I found I could cd into the directory where the deb file was and just use apt to achieve the same result.
# apt ./<the full deb file name>
It would appear that the maintainers have allowed dependencies for every eventuality. On the systemd side Devuan appears to allow packages to put their scripts into the systemd directory's and probably enable them which does nothing but make them happy because systemd doesn't fire. There are how ever a couple of systemd packages to beware of and I presume "systemd-sysv" is one of them. Am I correct? Selinux would be a set of packages to avoid too would it?
Thankyou for the reply it gives me some directions to keep digging in. I was worried with my ignorance of init systems there was some big glaring fact out there I had missed. It's only my desktop so no panic with the timing.
I previously have run sysvinit but installed runit on my desktop which had been running debian for some time as I kept up with a project I'm interested in. I run kvm-qemu for some of my tinkering and went to install libguestfs and it wanted to rip out runit and install sysvinit. Has anyone any idea why this is so and what difference in the systems is causing the need to change. I know very little about the init systems so did some reading but couldn't find anything. Of an interest running back on systemd wasn't a real happy experience. It would go for minutes getting to the login screen where as using sysvinit it took 18 seconds, and runit takes 7 seconds and both do it every time.
I've been using these,although I haven't done one onto bios but suspect they are fine due to earlier release. All seems to work as expected.
Only point I found was LXQT had to manually setup background etc. I don't know who that effects.
A different take on this discussion, try seeing it this way. IBM saw linux as possibly being their baby, so proceeded to help themselves, systemd was a simple business decision. The init system is the perfect place to start to gain control of linux, note all the bits and pieces that have followed. They all share one common trait, they are all for control of your computer, whether it be networking IO or FS. Also note the existing systems normally operated perfectly, but are just getting swept aside. The damning thing is Redhat has been profitable while they have done it, so they have made good money wrecking our system., they are laughing all the way to the bank. {>_<}
I don't know if I should be speaking up here as I have only been using Devuan for about 2 years, but I'm loving it and feel guilty that I'm not doing anything to help. I only came because I ran foul of systemd with some networking which they were taking over and limiting. So yes I'm putting my hand up if something needs doing, and I kind of figure there's a few more of us around too. So cheers to something really good.
Looks interesting but the link goes to a 404 page. Is there someway of acquiring the image? The pine64 Rockpro is a very versatile board and I have used a few but have wanted a simple cut down img with out all the bloat. BTW I'm lazy I should set to and study the SDK.
I gave the chimaera img for the Rpi4 a spin but wasn't able to connect to it again after update. Jumped over onto ther Geowulf and it worked great. Nice and clean just put on it what I needed. Playing round with libcamera and some of the alternatives for performance and quality of output. Great fun!
Pages: 1