Search results

I solved my problem: It was Docker running on that LXC container that issued a default docker network in the 192.168.0.0 subnet - it somehow missed that this range is in use. See the issue #37823 moby where it is described how to change the default docker0 network. After I stopped all...

What is strange is that the bridge is a loop to the host to itself: hostname -I >192.168.40.17 172.28.0.1 172.23.0.1 192.168.16.1 172.17.0.1 - 192.168.40.17 is the correct IP of the host - 192.168.16.1 is the IP where the internal bridge points to Inspect who 192.168.16.1 is, by verifying...

The background of the story is documented here. I have a LXC container that I cannot reach from a specific subnet, but I can reach it from other hosts (e.g. the router). The sleuthing led me down to identify the problem in the LXC container's routing setup. ip route default via 192.168.40.1...

I had the same problem, trying to install Gitlab in an unprivileged LXC with Debian. I also tried Ubuntu, because this issue suggests that it is not affected, but with the same result. However (and surprisingly), I was successfull running the official Gitlab Docker, inside Docker on LXC...

Yes, this was what I needed: Only map GID 33 to 1005 and UID 33 to 1005 - I wasn't able to leave out the other mappings since proxmox would complain that the mapping is invalid on startup.

I run into the exact same issue, with the same user-id combo. I checked every number twice, but I could not find the issue with my mapping. Then I removed the lxc.idmap completely from the CT conf, including entries in /etc/subuid and /etc/subgid - surprise: It did not make any difference, the...

[Edit] Eintrag korrigiert.. ich bin in einen Bug gelaufen, der angeblich schon 2019 gefixt wurde. Das führte dazu, dass die Einstellungen in der .conf keinen Effekt mehr hatten. Im Link oben ist ein workaround beschrieben, der für mich funktioniert hat. /etc/pve/lxc/100.conf lxc.idmap: u 0...

Habt ihr mittlerweile eine Lösung gefunden? Ich bin mit einem ähnlichen Problem beschäftigt. Ich habe ein samba-share mit 8TB, was ich gern im Nextcloud LXC als read-only folder und mit bind-mount verfügbar machen möchte. Was mir trotz sorgfältiger Lektüre der Doku nicht genau klar ist: Geht...

Solved: I somehow managed to create the user with the wrong GID on the proxmox host, e.g.: useradd nextcloud -u 1004 -g 1005 -m -s /bin/bash where it should have been: useradd nextcloud -u 1004 -g 1004 -m -s /bin/bash groupadd -g 1005 nas_user usermod -a -G nas_user nextcloud Now I can see...

I have successfully set up the Nextcloud Turnkey Container. It runs on an internal domain with automatic ACME DNS certs, it has its own Storage assigned and I am quite happy with it, so far. However, now I'd like to add an "External Storage" to the Nextcloud setup, from my Host system (proxmox)...