Econaut

The issue is with the container post-upgrade (bullseye > bookworm). Started a new ubunutu jammy instance and it has working dns. So for now I am just going to re-configure that one, reboot, & hope it sticks. Seems like the issue (if you want to reproduce) was regarding the upgrade itself. EDIT: Ran into another issue (ubuntu jammy container wont start up again after initial startup) - I added the lxc.mount.entry lines to the config after shutting it down. The debian bookworm container starts up with the same entries.

So I hit the same python 3.10 requirement (glibc2.35+) on debian bullseye (no surprise). I upgraded from bullseye to bookworm and added the unraidcgroup2 param & rebooted. All looks fine in the system except the WAN stopped working (apt, wget, etc). Worked fine prior to the upgrade. LAN connections still work fine. Looks like the resolv.conf file (resolve service) got removed. /run/systemd/resolve is missing. Manually grabbed the .deb and installed but domain resolution is still broken >.< Any ideas? Manually adding IP <> domain entries into /etc/hosts works but is unsustainable.

Ahh, I noticed the missing / but thought it was a typo - thanks for clarifying that it wasn't haha. Working now!

What would mimic the Read/Write - Slave access type? (two of my maps are remote shares - /mnt/remotes/... Alright so mkdir first in lxc container - as root? The host is root user AFAIK. EDIT: Hmm... I've added 3 and none worked (not seeing any mounted data in the container Should it be mnt/user/YOURSHARE mnt/PATHINLXC or /mnt/user/YOURSHARE /mnt/PATHINLXC

I added a new ubuntu jammy container (added fine) but it cannot start. Only log data I see is: Says it started but it doesn't start. Edit: seems to work fine with debian bullseye How does one map paths like docker?

6.11.5 - running it on bare metal works fine but the two dockers I tried have an issue with python3. (complaining about glibc). Installed python `sudo apt install python3` - something like that

Oh oops - the Debian Bullseye one

I'm unable to run python functions due to the GLIBC version being too low (2.31 - should be 2.35+) How can that be updated?

Is there any way to recover from an unresponsive UI via terminal? I can SSH in but the web UI is totally unresponsive. All I did was hit apply after changing one option on a docker container...

So here's where it's at now form zero usage since restarting a couple days ago: 1.3% 1.204GiB / 30.82GiB After restarting it's around 190MB Logging shows this and timeouts: [22-06-06 11:51:49.0415] Slim::Networking::Discovery::Players::_players_error (144) Unable to get players: Connect timed out: [22-06-06 11:51:21.0983] Slim::Networking::Discovery::Players::_players_error (144) Unable to get players: Invalid JSON response: [

It's very tiny, mostly just use it for the streaming service integrations. I can post a screen again when it bloats but I restarted it as it was too high.

The Docker advanced view (shows current usage)

This has some pretty severe memory leak issues. Even when running unused from startup, after not very long (several days to a week) it goes from 190MB memory usage up to over 2GB.

How do you enable supervisor/add-ons menu on this docker... https://github.com/linuxserver/docker-homeassistant Why would there even be a gimped docker that doesn't have all the features...?

Enabling internal node and setting IP/name still not seeing it show up. Any ideas? Edit: had to use localhost instead of IP

What does 'Verify all the disk" do specifically? Is it good practice to run this after a clear?

How do you change the timezone for this ? Tried adding -e TZ= but it didn't appear to work.

Is there an alternative you can recommend for the posted question?

Still nothing, even after checking for updates. Web UI is still failing semi-frequently (going unresponsive). 4 times so far today...

I'm on the latest but I don't see those options.

Thanks - got them all back with that technique, phew...

Oh man... that works thanks - clever. I did stop & restart the service though and upon restarting, the dependent rebuilding containers also vanished... I assume the same method can be used to restore them?

Yeah the other ones were using this one as a network option. Can I manually edit the original config file I screwed up somewhere? I am pretty sure restarting docker service will result in the same. The ones auto-rebuilding weren't even started at the time.

Some other ones are stuck in auto-rebuild and I can't actually click any buttons on the bottom. Any way to stop that?

Help! I accidentally broke my container by adding this tag to the end of the repository line: Repository: binhex/arch-qbittorrentvpn:4.3.9-2-01 What did I do wrong? How do I undo it? The container completely vanished after applying this.