I m trying to install Rancher on a single server just to mak rancher-users #general

Title

fierce-monkey-81592

08/15/2022, 10:58 PM

I’m trying to install Rancher on a single server just to make running some dev ops on a single box easier. I’ve followed the instructions here: https://rancher.com/docs/rancher/v2.5/en/installation/other-installation-methods/single-node-docker/ but it doesn’t seem to work. It looks like core-dns won’t deploy and I can’t seem to create any other deployments either… they all just sit in “pending”…. not sure where to begin troubleshoot to resolve this issue!

square-orange-60123

08/15/2022, 11:03 PM

try using a specific tag of rancher, not

latest

. That way you end up with a released version.

Copy code

docker run -d --restart=unless-stopped --privileged -p 80:80 -p 443:443 -e CATTLE_BOOTSTRAP_PASSWORD=yourpassword123 rancher/rancher:v2.6.6 --trace

should work.

fierce-monkey-81592

08/15/2022, 11:06 PM

Ok… I’ll try that next… it looks like there was drama with running things on over ZFS so I’m moving things back to an EXT4 volume and we’ll see where it goes from there… I’ll try the specific version next!

Thanks!

👍 1

That doesn’t seem to be working either… it created the pod but don’t seem to start it, and there a no logs, not even anything telling me whats wrong.

It’ also seems to be creating “helm-operation-xxxxx” pods everyone 1 minute or so and they all just sit in pending.

Again with no logs… and I can’t seem to use the web based kube console, it just says “connecting” and never does anything.

square-orange-60123

08/15/2022, 11:20 PM

what version of docker, and what’s your hardware?

fierce-monkey-81592

08/15/2022, 11:22 PM

The hardware is an old HP Proliant server running Ubuntu 20.04, and it’s docker version 20.10.17

Running the kubectl command locally on the box with the downloaded config, it is able to access the k3s instance running and I can issue commands.

Just no idea why things are stuck.

creamy-pencil-82913

08/15/2022, 11:36 PM

do you perhaps not have enough resources to schedule everything? how much cpu/memory does the box have? what do you get from

kubectl describe node

fierce-monkey-81592

08/15/2022, 11:39 PM

It’s pretty huge, dual 20 processors 96G ram

Docker is actually working on the same node fine, with other standalone containers

4 Views