Closed pratikbin closed 2 years ago
I don't think we've ever tested on Manjaro; it sounds like their Docker installation might be customized somehow, in a way that's not compatible with Kubernetes?
I'm particularly confused by this line:
E0726 19:43:46.387880 602560 docker_service.go:416] "Streaming server stopped unexpectedly" err="listen tcp 10.43.164.71:0: bind: cannot assign requested address"
It sounds like the kubelet is unable to set up docker networking. Do you have other things already running in Docker on this node?
Yeah one container is running.
Well I tried after clearing docker containers, still same last error @brandond FYI, I didn't tweak anything in docker.
This could be?
W0726 18:24:32.423122 444609 manager.go:159] Cannot detect current cgroup on cgroup v2
I'm not sure, sorry. I don't think I've seen anyone else try to get it working with the Docker runtime on Manjaro. Can I ask why you're using Docker instead of containerd?
Long story short, I'm having doubt that concourse worker behaving weird/having issues in containerd, so wanted to test that in docker with a bunch of other things.
You might try again with one of the distros we test against - RHEL/CentOS, Ubuntu, etc.
I have run into this same problem on Debian 11, but
curl -sfL https://get.k3s.io | sh -s - --kubelet-arg 'cgroup-driver=systemd' --docker
did work for me thanks @pratikbalar
Note: you don't actually need docker to run k3s in your nodes, it is deprecated
This repository uses a bot to automatically label issues which have not had any activity (commit/comment/label) for 180 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the bot can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the bot will automatically close the issue in 14 days. Thank you for your contributions.
Environmental Info: K3s Version: v1.21.3+k3s1
Node(s) CPU architecture, OS, and Version: Linux ctos 5.9.16-1-MANJARO #1 SMP PREEMPT Mon Dec 21 22:00:46 UTC 2020 x86_64 GNU/Linux, 16GB, i5 10thGen,
Cluster Configuration: Single Node with Docker runtime
Describe the bug: Want to run k3s with docker runtime 1st try:
curl -sfL https://get.k3s.io | sh -s - --docker
2nd try: add kubelet flag
curl -sfL https://get.k3s.io | sh -s - --kubelet-arg 'cgroup-driver=systemd' --docker
3rd disable service lb and traefik
curl -sfL https://get.k3s.io | sh -s - --kubelet-arg 'cgroup-driver=systemd' --docker --disable traefik --disable servicelb
Steps To Reproduce:
Expected behavior: it should run
Backporting not sure