The netstat shows that the k3s process is working.
Code
root@omv4-1:~# netstat -tulpn | grep k3s
tcp 0 0 192.168.100.145:2380 0.0.0.0:* LISTEN 1574528/k3s server
tcp 0 0 192.168.100.145:2379 0.0.0.0:* LISTEN 1574528/k3s server
tcp 0 0 127.0.0.1:10248 0.0.0.0:* LISTEN 1574528/k3s server
tcp 0 0 127.0.0.1:10249 0.0.0.0:* LISTEN 1574528/k3s server
tcp 0 0 127.0.0.1:10256 0.0.0.0:* LISTEN 1574528/k3s server
tcp 0 0 127.0.0.1:10257 0.0.0.0:* LISTEN 1574528/k3s server
tcp 0 0 127.0.0.1:10258 0.0.0.0:* LISTEN 1574528/k3s server
tcp 0 0 127.0.0.1:10259 0.0.0.0:* LISTEN 1574528/k3s server
tcp 0 0 127.0.0.1:6444 0.0.0.0:* LISTEN 1574528/k3s server
tcp 0 0 127.0.0.1:2380 0.0.0.0:* LISTEN 1574528/k3s server
tcp 0 0 127.0.0.1:2381 0.0.0.0:* LISTEN 1574528/k3s server
tcp 0 0 127.0.0.1:2382 0.0.0.0:* LISTEN 1574528/k3s server
tcp 0 0 127.0.0.1:2379 0.0.0.0:* LISTEN 1574528/k3s server
tcp6 0 0 :::6443 :::* LISTEN 1574528/k3s server
tcp6 0 0 :::10250 :::* LISTEN 1574528/k3s server
tcp6 0 0 :::10260 :::* LISTEN 1574528/k3s server
Display More
But ports 8080, 8443, 4443 are not occupied by anyone.