Channels
academy
amazon
arm
azure
cabpr
chinese
ci-cd
danish
deutsch
developer
elemental
epinio
espanol
events
extensions
fleet
français
gcp
general
harvester
harvester-dev
hobbyfarm
hypper
japanese
k3d
k3os
k3s
k3s-contributor
kim
kubernetes
kubewarden
lima
logging
longhorn-dev
longhorn-storage
masterclass
mesos
mexico
nederlands
neuvector-security
office-hours
one-point-x
onlinemeetup
onlinetraining
opni
os
ozt
phillydotnet
portugues
rancher-desktop
rancher-extensions
rancher-setup
rancher-wrangler
random
rfed_ara
rio
rke
rke2
russian
s3gw
service-mesh
storage
submariner
supermicro-sixsq
swarm
terraform-controller
terraform-provider-rancher2
terraform-provider-rke
theranchcast
training-0110
training-0124
training-0131
training-0207
training-0214
training-1220
ukranian
v16-v21-migration
vsphere
windows
Title
c
curved-grass-88767
08/05/2022, 9:52 PMI have a demo next week and on my environment (2 Ubuntu VMs, 1 rund Rancher the other a single node cluster) I see that when the VM with the single node cluster reboots it fails to restart the K8s cluster. I see some of the containers come up in docker ps for a few seconds but then they die right away.
Anyone got a pointer how to troubleshoot this?
p
polite-piano-74233
08/05/2022, 10:12 PMubuntu version?
if 22.04 do
sudo nano /etc/default/grubGRUB_CMDLINE_LINUX="cgroup_memory=1 cgroup_enable=memory swapaccount=1 systemd.unified_cgroup_hierarchy=0"sudo update-grub
sudo rebootc
curved-grass-88767
08/05/2022, 10:44 PMI got 20.04
Nevertheless the issue is resolved I had a conflicting Docker version installed using snap during installation of the VM, which clashed with the one I installed afterwards.
👍 1