Privileged container network issue.

V

vrlm

New Member
Jan 19, 2025
1
0
1
Does anyone knows why privileged lxc container might not be able to have network connectivity?

I did two identical containers with vanilla default settings. The ONLY difference between two containers, is the fact that one of them is privileged and another one is not.

Privileged container can not resolve any network related requests. Running apt update I get this response

root@lxc-jellyfin:/# apt update
Ign:1 http://archive.ubuntu.com/ubuntu oracular InRelease
Ign:2 http://archive.ubuntu.com/ubuntu oracular-updates InRelease
Ign:3 http://archive.ubuntu.com/ubuntu oracular-security InRelease
Ign:1 http://archive.ubuntu.com/ubuntu oracular InRelease
Ign:2 http://archive.ubuntu.com/ubuntu oracular-updates InRelease
Ign:3 http://archive.ubuntu.com/ubuntu oracular-security InRelease
Ign:1 http://archive.ubuntu.com/ubuntu oracular InRelease
Ign:2 http://archive.ubuntu.com/ubuntu oracular-updates InRelease
Ign:3 http://archive.ubuntu.com/ubuntu oracular-security InRelease
Err:1 http://archive.ubuntu.com/ubuntu oracular InRelease
Temporary failure resolving 'archive.ubuntu.com'
Err:2 http://archive.ubuntu.com/ubuntu oracular-updates InRelease
Temporary failure resolving 'archive.ubuntu.com'
Err:3 http://archive.ubuntu.com/ubuntu oracular-security InRelease
Temporary failure resolving 'archive.ubuntu.com'
All packages are up to date.
Warning: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/oracular/InRelease Temporary failure resolving 'archive.ubuntu.com'
Warning: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/oracular-updates/InRelease Temporary failure resolving 'archive.ubuntu.com'
Warning: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/oracular-security/InRelease Temporary failure resolving 'archive.ubuntu.com'
Warning: Some index files failed to download. They have been ignored, or old ones used instead.
root@lxc-jellyfin:/#




I have not fiddled with any networks settings. I even replicated that issues by continuously deleting container and reinstalling it. Each time privileged container have connectivity issues and unprivileged works totally fine.

Has anybody encountered that issue or have an idea what could be the problem ?
 
Show ip a output for container.
Is it only a DNS issue or does it have no NW connection at all? Have you tried pinging using numeric IP address only?

vrlm said:
The ONLY difference between two containers
Click to expand...
Have you checked for a NW conflict, same MAC addresses etc.?

If you show the pct config <CTID> output of both LXCs - maybe someone can help you.
 
I joined the forum just now to pile on to this issue. In the last few days I’ve created and destroyed 8 plain vanilla Debian and one Ubuntu containers to host Plex because the containers keep failing at starting the networking service. I’ve tried dhcp I’ve tried static ip. Pinging 8.8.8.8 works fine but I can’t access the Plex dashboard or anything.
 
I am also having issues: I tested UbuntuServer 22, 23, 24, Debian 12, and I selected unprivileged and privileged. I found that creating a new container with Ubuntu24 did not complete the boot cycle. I got a black screen with just a cursor. When I checked my router, no IP was showing. This was all with DHCP for IPv4. IPv6 was left static. NOTE that I was able to "pct enter id"
 
JennyLucas said:
I am also having issues: I tested UbuntuServer 22, 23, 24, Debian 12, and I selected unprivileged and privileged. I found that creating a new container with Ubuntu24 did not complete the boot cycle. I got a black screen with just a cursor. When I checked my router, no IP was showing. This was all with DHCP for IPv4. IPv6 was left static. NOTE that I was able to "pct enter id"
Click to expand...
this sounds like my issue. when you PCT enter'd the container, did you check "systemctl status" to see what was delayed/failed? for me, it was networking.service.

though, when you say you left your IPv6 static, did you assign anything? that could be causing a separate issue.
 
Closing the loop on my related issue, one of the other comments made me go back and look at my ipv6 settings. i was setting ipv6 to dhcp as per the instructions i was following to set up the Plex server, but what resolved my issue was setting ipv6 to static and leaving it blank, i.e. "None". then, my networking service issues went away.
 
I didn't check systemctl for errors. As for IPv6, I left it static and blank.

I'm suspicious of networking due to no IP being assigned.

I'm just going to use Debian 12 as a workaround.

I have deleted the non-working instances. All of them infortunately. I just tried again and they worked. Darn. If I see the issue again, I will post the config.
 
You must log in or register to reply here.
Top Bottom