u/thestoiccoder

So I'm on Gentoo and I am currently using podman with distrobox.

Every time I create a container then try to stop it I get this warning/error:

WARN[0010] StopSignal SIGTERM failed to stop container "container-name" in 10 seconds, resorting to SIGKILL

I can attempt to stop the container using distrobox and still experience the same thing. I then check to see if it has stopped, but it never is. For now, the only way I can truly stop a container is using the "podman kill" command.

I like using this with Distrobox as I can containerize different linux distro dev environments, and this has been occurring regardless of what image I pull. I really like using Podman and I'd hate to have to go back to Docker because of this. With all the research I've done on this problem, I've lost count on how many other cases I've found where people have experienced this exact same problem, without getting any kind of hint or lead as to how to go about fixing this.

Of course any advice or feedback would be greatly appreciated. Many thanks in advance.

So I've been on Gentoo for a little over a month now, and for the most part when it comes to containers I've always used Distrobox and Podman/Docker.

Ever since I moved to Gentoo, Distrobox has been kinda buggy (either with Podman or Docker), and I've recently learned about Incus and wanted to try it.

At this point I can't even get started with it due to whenever I use the "incus admin init" command I get this error at the end:

'Error: Failed to create local member network "incusbr0" in project "default": Failed clearing firewall: Failed clearing nftables rules for network "incusbr0": EOF'

I've also recently read in several places where people have stated that Docker doesn't play well with Incus, so I've completely cleaned out everything Docker and Distrobox related. I even tried different versions of Incus with creating all the necessary files for each version in "/etc/portage/".

Just out of curiosity, I fired up a linux mint VM on my proxmox server and installed it there no problem.

My knowledge of networking is very limited and I'd sure love to get this fixed. I've already been struggling with this for the past 2 days.

Of course any advice or feedback would be greatly appreciated. Many thanks in advance.

Being a programmer and as the title says; I'm curious if anybody else uses LXC containers on a daily driver?

With most of the research I've done, I've found that people usually refer to LXD and LXC within the context of servers, homelabs, Proxmox, TrueNAS, etc..

And that's all well and good but, I've been wondering if this potential solution is an uncommon one?

I've been using Distrobox for a long time, but have grown weary with its and Podman's bugginess.

Docker is okay, but I still don't like the idea of it slowly polluting my host system over time, and I'm considering something more isolated. I really like being able to spin up a lightweight linux distro where I can build and test things, then throw it away when I'm done.

But is it possible that LXC containers aren't meant for this use case? And if I understand correctly; LXC is slightly heavier than Podman or Docker?

Any advice or feedback would be greatly appreciated. Many thanks in advance.

So I'm on a clean install of Void (as a new user), and I recently installed Distrobox with the standard curl command. During some research and earlier issues, I added these lines to the registries.conf file so it knew where to pull images:

unqualified-search-registries = ["docker.io", "quay.io", "ghcr.io"]
short-name-mode = "enforcing"

After that small success I'm still experiencing this error as described below:

Error: unable to start container "...": runc: runc create failed: unable to start container process: unable to apply cgroup configuration: rootless needs no limits + no cgrouppath when no permission is granted for cgroups: mkdir /sys/fs/cgroup/...: permission denied: OCI permission denied

After some more research, I added these lines to the "/etc/containers/containers.conf" file in hopes to alleviate the error (also had to install crun):

[engine] 
cgroup_manager = "cgroupfs" 
runtime = "crun" 

[containers] 
cgroups = "enabled" 
pidns = "private" 
userns = "private" 
netns = "private" 
ipcns = "private" 
utsns = "private"

I noted the runtime line and changed it to "runc" just to test, and still the same thing! For 2 days now this issue has been driving me crazy.

Any advice or feedback would be greatly appreciated. Many thanks in advance.

On Void Linux I have Flatpak installed and setup.

And while everything works as you would think, I have noticed some very irritating behavior whenever I try to install something.

For example, when I installed Flatseal I had to enter in my password over and over when it was going through all its dependencies. I lost count on how many times I had to enter it because it was so many!

Of course the only way to overcome this is to use sudo.
I've used plenty of other distros and never experienced this before. And whenever I start a new installation, one of the first things I adjust is the sudoers file, so I know I'm in the wheel group. I've been wracking by brain as to what else it could be?

Any advice or feedback is always greatly appreciated. Many thanks in advance.

So I decided to give Void Linux another try.
Not too long ago, I had no problems installing Void with the base install, but this time I had to go with the xfce version. I originally didn't want to have to do this as my goal was to install i3, so now here I am removing everything having to do with xfce.

I have no clue on what happened during the process of setting up this laptop. It has been nearly 2 days now and I've been pulling my hair out trying to figure out if I accidentally deleted a necessary package, or didn't install one in the first place.

And now I can't open Wezterm. I keep getting an XOpenDisplay error where the display won't open. And the main reason as to why I know this was because at the time, to make things simpler I was connected to the laptop through SSH from another computer and I stumbled across this strange behavior. At the time Wezterm was the only terminal I had installed on it and using sudo is the only janky thing that appears to work around this issue. And even then it doesn't appear to use my config file.

Just to test, I re-installed xfce4-terminal and that appears to open just fine directly on the laptop with i3. I also recently noticed similar behavior trying to open Gparted (only sudo works). Applications like firefox and thunar open just like you would expect it to.

To give a clearer picture, I'm attempting to go as minimal as possible; so for example I'm using startx instead of using lightdm.

Any help or advice would be greatly appreciated. Many thanks in advance.

EDIT: I've been doing some more research, and while I can admit that I don't completely understand how it worked, I installed some potentially missing vulkan drivers and now Wezterm opens! However, I still can't get Gparted to open without sudo. Could this have something to do with some kind of missing GTK package? I know that on my other computer (which is currently running EndeavourOS), if I use rofi to open up Gparted I at least get an authentication window prompt before it opens.