This message was deleted.
# k3sa
adamant-kite-43734
09/30/2022, 7:34 AMThis message was deleted.
m
melodic-hamburger-23329
09/30/2022, 7:42 AMhm, rerun with updated install script and it seems it was able to recover the containers. Not sure if using old install script was the culprit
c
creamy-pencil-82913
09/30/2022, 7:49 AMI have literally never seen that error from containerd. It’s trying to access a registry while creating the snapshotter during startup?
creamy-pencil-82913
09/30/2022, 7:49 AMand it got a 404 from it?
m
melodic-hamburger-23329
09/30/2022, 7:50 AMI’m using internal registry and basically block access to dockerhub, etc. Maybe the mirror configuration somehow gets messed up during upgrade
c
creamy-pencil-82913
09/30/2022, 7:51 AMare you also using one of the non-standard snapshotters? btrfs or stargz or something?
creamy-pencil-82913
09/30/2022, 7:51 AMI would probably go create an issue on the containerd GH repo if you see it again.
m
melodic-hamburger-23329
09/30/2022, 7:51 AMstargz yes
c
creamy-pencil-82913
09/30/2022, 7:52 AMyeah, probably a bug in that then.
m
melodic-hamburger-23329
09/30/2022, 7:52 AMhmm
c
creamy-pencil-82913
09/30/2022, 7:52 AMI would grab the full containerd logs and create an issue
creamy-pencil-82913
09/30/2022, 7:52 AMI don’t think hardly anyone uses stargz
creamy-pencil-82913
09/30/2022, 7:52 AMso they’d probably appreciate the report
☝️ 1
creamy-pencil-82913
09/30/2022, 7:53 AMb
bulky-sunset-52084
10/01/2022, 2:36 AM
Also if it makes your life easier (kinda unrelated) rancher has a tool for upgrading k3s clusters in an automated fashion: https://github.com/rancher/system-upgrade-controller
m
melodic-hamburger-23329
10/02/2022, 11:21 PM@bulky-sunset-52084 Yes, I tried it but couldn’t find working configuration
b
bulky-sunset-52084
10/03/2022, 3:28 AM
12 Views