concourse / concourse/concourse-chart
Concourse worker pod is crashing on Minikube/Kind cluster in Mac
Open
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 160
- Forks
- 189
- PR merge metrics
- No merged PRs in 30d
Description
After install following worker pod is not working
oncourse-worker-0 0/1 CrashLoopBackOff 12 (3m8s ago) 161m
concourse-worker-1 0/1 CrashLoopBackOff 12 (3m20s ago) 161m
And their failure logs
{"timestamp":"2022-03-10T08:03:01.566080500Z","level":"info","source":"guardian","message":"guardian.start.completed","data":{"session":"6"}} │
│ {"timestamp":"2022-03-10T08:03:01.566194300Z","level":"error","source":"guardian","message":"guardian.starting-guardian-backend","data":{"error":"bulk starter: mounting subsystem 'cpuset' in │
│ bulk starter: mounting subsystem 'cpuset' in '/sys/fs/cgroup/cpuset': operation not permitted │
│ bulk starter: mounting subsystem 'cpuset' in '/sys/fs/cgroup/cpuset': operation not permitted
Any idea
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Helm chart installation on a Minikube or Kind cluster on macOS and inspect the worker pod logs, especially the Guardian cpuset mount failure. Trace the worker configuration in the chart and determine what change is needed for the pods to start; done means both worker pods become Ready without CrashLoopBackOff.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100