https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rke2
a
This message was deleted.
c
k
thanks, that was it
Copy code
[root@simplek8s /]# rke2-killall.sh 
[root@simplek8s /]# rm -rf /var/lib/rancher
[root@simplek8s /]# umask 0000
[root@simplek8s /]# rke2 server
did the trick so far
c
Why are y’all running RKE2 from the command line?
My understanding is that the umask for systemd units should be normal, the stig hardening just affects interactive shell umasks
but I’m confused why ya’ll are running rke2 from an interactive shell instead of just starting the systemd unit.
k
for some reason there is no systemd unit yet, been following (I think) the instructions for air gap install
Following the steps from here... https://docs.rke2.io/install/airgap I downloaded all the dependencies from a build system and installed them via yum localinstall on the airgapped machine, downloaded the rke2-images.linux-amd64.tar.gz and docker load, tag and push to the private registry and then use the binary with the system-default-registry: "registry.example.com:5000" flag set
so starting to think I might do over and try the install.sh script install method? the binary install from a private registry doesn't seem to create the systemd service
c
The binary does not create a systemd unit, no - that is handled by the install script. If you are downloading things manually then you would also have to download the systemd unit file as well. You can find the server and agent unit files at https://github.com/rancher/rke2/tree/master/bundle/lib/systemd/system
👍 1
k
thanks, I will give the script method a shot as well
52 Views
Open in Slack
PreviousNext
Powered by