Update/upgrade issues after adding new container

[InfectFTW]

Hi,

I'm very new to proxmox and am facing some issues currently.
I want to install vaultwarden to self host my password file but the problem are only related to proxmox.

I added a new container for Nginx like I've seen it in a youtube tutorial (Ubuntu 23.10 template, ID 900, 2 cores, 512mb RAM, 6GB storage, static IP/24)
After starting the container I did apt-get update but then I get some errors:

root@NginxVaultwarden:~# apt-get update
Ign:1 http://archive.ubuntu.com/ubuntu mantic InRelease
Ign:2 http://archive.ubuntu.com/ubuntu mantic-updates InRelease
Ign:3 http://archive.ubuntu.com/ubuntu mantic-security InRelease
Ign:1 http://archive.ubuntu.com/ubuntu mantic InRelease
Ign:2 http://archive.ubuntu.com/ubuntu mantic-updates InRelease
Ign:3 http://archive.ubuntu.com/ubuntu mantic-security InRelease
Ign:1 http://archive.ubuntu.com/ubuntu mantic InRelease
Ign:2 http://archive.ubuntu.com/ubuntu mantic-updates InRelease
Ign:3 http://archive.ubuntu.com/ubuntu mantic-security InRelease
Err:1 http://archive.ubuntu.com/ubuntu mantic InRelease
  Temporary failure resolving 'archive.ubuntu.com'
Err:2 http://archive.ubuntu.com/ubuntu mantic-updates InRelease
  Temporary failure resolving 'archive.ubuntu.com'
Err:3 http://archive.ubuntu.com/ubuntu mantic-security InRelease
  Temporary failure resolving 'archive.ubuntu.com'
Reading package lists... Done
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/mantic/InRelease  Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/mantic-updates/InRelease  Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/mantic-security/InRelease  Temporary failure resolving 'archive.ubuntu.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.

On google I found an answer that this is probably a DNS problem.
To be fair: I already installed AdGuard on proxmox.
To solve this problem I stopped the AdGuard container, used 1.1.1.1 as DNS in my FritzBox and did a restart of the FritzBox and Proxmox.
Unfortunately the issue is still there.

Do you have an idea what could be my problem?

My hardware: HP Elitedesk 800 G5, i5-9500T, 16GB RAM, 256GB SSD

 

[KevinS]

Yeah this is definitely a network issue. Can you ping from the counter to any public IP? (for example 1.1.1.1)
If that works but DNS isn't:
What's in your /etc/network/resolv.conf ?

In case you can't ping public IPs, make sure

ip route

shows your default gateway as your fritzbox (as i think that is probably your router for internet access) and your container has a static IP in that subnet.

 

[InfectFTW]

What do you mean with "from the counter"?

ping from proxmox server:

--- 1.1.1.1 ping statistics ---
18 packets transmitted, 18 received, 0% packet loss, time 17035ms
rtt min/avg/max/mdev = 9.198/11.449/14.993/1.470 ms

ping from nginxvaultwarden:

root@NginxVaultwarden:~# ping 1.1.1.1
ping: connect: Network is unreachable

resolve.conf is empty in proxmox overall and nginxvaultwarden container
Just to be sure, the command is "nano /etc/network/resolv.conf" right?

ip route proxmox:

default via 192.168.178.1 dev vmbr0 proto kernel onlink
192.168.178.0/24 dev vmbr0 proto kernel scope link src 192.168.178.35

192.168.178.1 is my gateway for my router (fritzbox)

ip route in nginx container doesn't show anything

I just wanted to check if the nginxvaultwarden container has a static IP and I've seen that this container is not visible in my router.
So I checked the network tab in proxmox for this container and there is also no IP entered.
This is probably the problem, right?

 

[KevinS]

Your network configuration on your container is the issue. Your router might only display ip addresses which they provide through dhcp, on the proxmox network tab your IP doesn't (have to) show up either

so your network configuration on your container is not correct, so you probably made a mistake in your configuration. Your /etc/network/interfaces file should look something like this (replace the X with your desired IP and check through ifconfig how your network adapter is actually called, in my case it's eth0):

# UNCONFIGURED INTERFACES
# remove the above line if you edit this file

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
 address 192.168.178.X
 gateway 192.168.178.1
 dns-nameservers 192.168.178.1
 hostname YOURHOSTNAME

afterwards (if necessary change the adapter name):

ifdown eth0
ifup eth0

Then your network configuration should work. If not please provide which steps you tried to follow in order to setup your static ip address

 

[InfectFTW]

Thank you for your help.
I took the easy way and deleted the bad container and added a new one.
This time it worked to update/upgrade