zyrex
Dabbler
- Joined
- Nov 20, 2019
- Messages
- 17
Thanks, I did try that work around now, but it made no difference unfortunately.I totally agree, should be 1000. However iX decided to change that, so we wonder why, because is not explained anywhere like you said very well. What if iX decides to use UID 1000 for something else internally. I found the UID issue yesterday, by pure accident, while helping an user fix his apps. This was a clean Bluefin install, I was like "Why the non-root user UID is 3000??" But they sure did fix the Debian.profile
, which was broken in Angelfish. I don't have answers to Why's but at least people are aware of these non-documented changes. My thread has a fix for the OP, see Kubernetes Service section. Let me know if that fixes the issue. I've been revising it every other day with new findings, like you said. Just trying to help.
And the log ends with the same as danb35 have;
Code:
Dec 20 08:15:25 megabyte k3s[50575]: E1220 08:15:25.583180 50575 kubelet.go:1397] "Failed to start ContainerManager" err="failed to initialize top level QOS containers: root container [kubepods] doesn't exist"
Guess I'll try and submit a bug, however, yesterday when I registered for the Jira-page, I ended up at a weird portal page, and I couldn't see all the other bugs I could before I signed in.