Cannot update PVE container from Community Scripts LXC

[syncdme]

I setup Syncthing in a container using Proxmox shell by using Community Helper Scripts ( Proxmox VE Helper-Scripts ) by running

bash -c “$(curl -fsSL ``https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/syncthing.sh``)”

and it’s working great for the most part. But I cannot seem to update it within the container. I’ve tried running sudo apt update, apt update, update…and it doesn’t seem to be finding the repos or something. For instance, running sudo apt update or apt updateI get

Ign:1 ``http://security.debian.org`` bookworm-security InRelease Ign:2 ``https://apt.syncthing.net`` syncthing InRelease Ign:3 http://deb.debian.org/debian` bookworm InRelease Ign:1 http://security.debian.org bookworm-security InRelease Ign:2 https://apt.syncthing.net syncthing InRelease Ign:4 http://deb.debian.org/debian bookworm-updates InRelease 0% [Connecting to security.debian.org] [Connecting to apt.syncthing.net]`

and running update I get

curl: (6) Could not resolve host: ``raw.githubusercontent.com

I am able to ping my other devices on the same network and I am able to ping 8.8.8.8. And it’s syncing fine with all of my devices, I’m just not able to reach out to update. Currently running v2.0.9.

Not sure what I’m missing.. Any help is appreciated!

[gadget]

@syncdme

and running update I get

curl: (6) Could not resolve host: ``raw.githubusercontent.com

That indicates a DNS resolution issue…

I am able to ping my other devices on the same network and I am able to ping 8.8.8.8. And it’s syncing fine with all of my devices, I’m just not able to reach out to update. Currently running v2.0.9.

I’m guessing you’re likely pinging your other network devices by IP address just like Google’s public DNS server at 8.8.8.8.

For Syncthing, peers are configured via static IP address, IP addresses derived via local discovery, and/or IP addresses derived via global discovery.

Not sure what I’m missing.. Any help is appreciated!

I suspect that if your LXC container pings Cloudflare’s primary public DNS at its IP address 1.1.1.1 it’ll succeed, but not if it pings its domain name one.one.one.one.

[syncdme]

@gadget ugh I am horrible at networking..that fixed it! You were right, I was not able to ping one.one.one.one. Changed my DNS from “use host settings” to manually input.

Thank you!