https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# general
a
This message was deleted.
b
Didn't hit this, but there's more information you can provide so that others can help out:
I found a k3s bug report that suggests
A link to that bug report would be helpful.
use --disable-network-policy.
There is just no way I see to set this flag.
k3s but you're doing podman? Which one is it? If k3s it's probably a flag for the initial bootstrap. Are you doing an HA cluster or a single node? What's your setup look like?
Looking at the k3s.log it stops with a fatal error about network policies.
Actual log examples would be helpful here.
If you have steps you're doing to reproduce the bug/error that would also be insightful in providing you with additional community support.
Whenever we try to start the 2.13.x container with the restored date from 2.12.3 it just boot loops.
The container is crashloop backoff or the box is boot looping?
b
The container just again and again tries to start k3s but fails and tries again.
Seems old and is closed but talks about what I see last in k3s.log.
b
The pod is trying to start k3s, you didn't do a k3s install and install rancher?
You should also say exactly what container images you're pulling and how you're starting it then.
b
I create the container. I restore the backup as per the instruciton for container based setups from a tar.gz.
b
(Also this is why podman/docker installs isn't supported)
If you made the container yourself, then you should reference the Dockerfile or Containerfile you used for it.
Lastly you should say what OS you're using
b
No , I mean I do a 
podman create
then I restore /var/lib/rancher from tar.gz
Then I try to run it.
The OS is Rocky Linux 9.
b
podman create still uses a container image
b
Yeah. the official one.
b
You say official, but in my experience saying exactly what command you're running gets you the best help
what's the output of 
getenforce
on Rocky?
b
SELinux is on.
b
Try turning it off and re-run all the commands to see if it can then grok the ipv4 address
b
hmm. I try that.
Copy code
sudo podman create --name rancher-2-13-2  -v /etc/letsencrypt/live/rancher.machine-deck.jeffries-tube.at/fullchain.pem:/etc/rancher/ssl/cert.pem  -v /etc/letsencrypt/live/rancher.machine-deck.jeffries-tube.at/privkey.pem:/etc/rancher/ssl/key.pem  -e HTTP_PROXY="<http://192.168.1.250:8080>"  -e HTTPS_PROXY="<http://192.168.1.250:8080>"  -e NO_PROXY="localhost,127.0.0.1,0.0.0.0,10.0.0.0/8,cattle-system.svc,.svc,.cluster.local,192.168.1.0/24"  -e no_proxy="localhost,127.0.0.1,0.0.0.0,10.0.0.0/8,cattle-system.svc,.svc,.cluster.local,192.168.1.0/24"  --privileged  -p 10080:80 -p 10443:443 --log-driver journald  --replace rancher/rancher:v2.13.2 --no-cacerts
b
I've never tried running rancher via the container (which all the docs say should only be for testing/eval and not production) but there might be a clue in there for those in the know.
The other thing you can do is set up Rocky as a single k3s node, install rancher the supported way, then import the etcd backup.
If turning SELinux to permissive doesn't work.
b
That was my next idea if there is no one that has similar problems and better luck solving it.
b
Honestly it's gonna be the better thing for you in the long run.
But I don't know your circumstances
35 Views
Open in Slack
PreviousNext
Powered by