dashboard: `CreateContainerConfigError` on 0.7.0 release on docker
Describe the bug
Dashboard pod wont go into ready state
Has error CreateContainerConfigError in status
Expected behaviour
It doesnt happen
Steps to reproduce the bug
Install 0.7.0 release on docker
Environment details
- Kubernetes Platform:
docker
- Kubernetes or OpenShift version:
- Install mode (if on OpenShift):
- Cloud-provider/provisioner:
- Versions:
- Tekton Dashboard:
0.7.0
- Tekton Pipelines:
- Tekton Triggers:
- Install namespaces:
- Tekton Dashboard:
- Tekton Pipelines:
- Tekton Triggers:
Additional Info
Dashbaord pod status
tekton-dashboard-95969f65b-fl9h5 0/1 CreateContainerConfigError 0 5m32s
Output from describe dashboard pod
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 84s default-scheduler Successfully assigned tekton-pipelines/tekton-dashboard-95969f65b-fl9h5 to docker-desktop
Normal Pulling 83s kubelet, docker-desktop Pulling image "gcr.io/tekton-releases/github.com/tektoncd/dashboard/cmd/dashboard@sha256:1a44d51696970ec16981eeada03c45e73b202d87a680c0a93f6fc3e27f8798b4"
Normal Pulled 73s kubelet, docker-desktop Successfully pulled image "gcr.io/tekton-releases/github.com/tektoncd/dashboard/cmd/dashboard@sha256:1a44d51696970ec16981eeada03c45e73b202d87a680c0a93f6fc3e27f8798b4"
Warning Failed 10s (x7 over 73s) kubelet, docker-desktop Error: container has runAsNonRoot and image will run as root
Normal Pulled 10s (x6 over 72s) kubelet, docker-desktop Container image "gcr.io/tekton-releases/github.com/tektoncd/dashboard/cmd/dashboard@sha256:1a44d51696970ec16981eeada03c45e73b202d87a680c0a93f6fc3e27f8798b4" already present on machine
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 17 (17 by maintainers)
https://github.com/tektoncd/dashboard/blob/a1c6711f5692d358918b60b6cab82fda71578a8c/tekton/build.yml#L49
It’s not going to copy hidden files (those that begin with a
.) !It’s in the plumbing repo. I’m on my phone now, can give you a link later if you cannot find it.
That’s it, it’s not a nonroot image
We shouldn’t need it at all as we’re using a
nonrootbase image. I will dive in the released image to see what happens.