Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

On Kubernetes, a workspace pod ends up in CrashLoopBackoff if devcontainer repo not found #16

Closed
sharkymark opened this issue May 22, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@sharkymark
Copy link

I have a coder_parameter to let an engineer select a devcontainer repo.

If the value is incorrect, the workspace says running, but the pod is in Error then CrashLoopBackoff status

Video replay
https://www.loom.com/share/6ba26de24a47460889533b264b5f3857

@sharkymark sharkymark added the bug Something isn't working label May 22, 2023
@sharkymark
Copy link
Author

I added

      env {
        name = "FALLBACK_IMAGE"
        value = "ubuntu:latest"
      }

And the FALLBACK_IMAGE only works if I did not have a Dockerfile in the .devcontainer directory.

The UI logs didn't show a message that I was expecting from looking at envbuilder.go which is no Dockerfile or devcontainer.json found:

If I did not have a devcontainer.json, the pod fails and the agent never comes up (UI)

@bpmct @kylecarbs

@kylecarbs
Copy link
Member

Just fixed this!

New tag is coming out v0.0.6 😎

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants