-
-
Notifications
You must be signed in to change notification settings - Fork 452
[BUG] #1139
Replies: 1 comment · 5 replies
-
Hi @ashersilver , thanks for starting this discussion! Can you please provide some more info on why the calico-node pods are failing? |
Beta Was this translation helpful? Give feedback.
All reactions
-
Ok I ran the following
The problem appears to be something related to shared volumes, - I saw something similar in another bug reported by another user here Here's what I got its probably only the log entries at the end which are useful:
|
Beta Was this translation helpful? Give feedback.
All reactions
-
Thank you! |
Beta Was this translation helpful? Give feedback.
All reactions
-
Maybe this helps? #479 |
Beta Was this translation helpful? Give feedback.
All reactions
-
Thanks I tried that, but it goes deeper .. that issue wi the sharing is /sys/fs and I tried the code
when I restart the container in Docker, and I log in via a shell using docker exec -it, it appears to succeed in sharing the /sys/fs/bpf folder r-x for all but the issue I am experiencing is actually for /sys/fs not being shared above. I don't know cilium, but ultimately I am installing k3s with calico to be able to work with Istio .. I have a horrible feeling it comes down to incompatibilities with MacOS and linux and the lack of support for servicectl (linux) in macOS (launchctl). restarted all pods in sight after the new commands above... seems some progress...
I suspect this might be easier on Ubuntu 20.4 |
Beta Was this translation helpful? Give feedback.
All reactions
-
If you're still working on this I've been running into this issue too. I haven't fully solved it but I've gotten past it failing on I am working on Ubuntu 22.04.1, not macOS, but I think that this problem is distinct from the Note that with Now the pod hangs at
with changing pod ids each time. Do you get that error as well? |
Beta Was this translation helpful? Give feedback.
All reactions
This discussion was converted from issue #1128 on August 29, 2022 10:45.
-
What did you do
Trying to get k3d cluster started, disable flannel and enable calico on k3s
(next step to install Istio and CN postgres once this is working. Need calico to permit greater consistency with k8s network policy)
kubectl get pods -n kube-system
Restarted docker, rebooted, removed all old unused docker images, restarted, retried with 1 agent, no api-port etc.
What did you expect to happen
cluster to start with 1 server, 3 agents
Screenshots or terminal output
Which OS & Architecture
macOS Monterrey 2020 16" MBP 16GB; Docker 4.11.1 with 9 GB, 3GB swap 6 processors
k3d runtime-info
Which version of
k3d
1.24 k3s 1.24.3
k3d version
Which version of docker
4.11.1 build 84025
docker version
anddocker info
docker info
Beta Was this translation helpful? Give feedback.
All reactions