Add support for devcontainers

[Kidswiss]

Summary

• Adds support for devcontainers to streamline the dev ux

Checklist

• Categorize the PR by setting a good title and adding one of the labels:
  bug, enhancement, documentation, change, breaking, dependency
  as they show up in the changelog
• Update tests.
• Link this PR to related issues.

[wejdross]

I like it a lot, it'll grow with time for sure with some customizations and aliases, but I'm ok with that, I think it might make even bigger sense to make dev container with necessary tooling etc. for components, so we have correct jsonnets, commodore etc. that should shorten onboarding drastically

[wejdross]

small request from my side:

alias ka='kubectl --as cluster-admin'
alias kwp='watch -n 0.1 kubectl get pod'
alias kwo='watch -n 0.1 kubectl get object'
alias kwoa='watch -n 0.1 kubectl --as cluster-admin get object'

[wejdross]

alias of ll is also missing in bash spec

[Kidswiss]

You can add your own aliases via dotfiles. I wouldn't clutter the defaults too much, as everybody wants different things.

Here's an example of my dotfiles: https://git.earthnet.ch/simon.beck/devcontainerdotfiles/src/branch/main/zshrc

[wejdross]

the only thing is that rebuilding is enforced and it takes time to achieve, on metered connections it can take ages, maybe we could think of some caching in kindev?

[Kidswiss]

the only thing is that rebuilding is enforced and it takes time to achieve, on metered connections it can take ages, maybe we could think of some caching in kindev?

What do you mean by "rebuilding is enforced"? Once the container is built you can simply start it.

[wejdross]

the only thing is that rebuilding is enforced and it takes time to achieve, on metered connections it can take ages, maybe we could think of some caching in kindev?

What do you mean by "rebuilding is enforced"? Once the container is built you can simply start it.

but any interruption, change to dotfiles, oom, whatever will result in rebuilding whole container, this is something I don't like, I can't find any docs, how to shutdown gracefully (keep container in background) and shutdown IDE for exmaple.

[Kidswiss]

the only thing is that rebuilding is enforced and it takes time to achieve, on metered connections it can take ages, maybe we could think of some caching in kindev?

What do you mean by "rebuilding is enforced"? Once the container is built you can simply start it.

but any interruption, change to dotfiles, oom, whatever will result in rebuilding whole container, this is something I don't like, I can't find any docs, how to shutdown gracefully (keep container in background) and shutdown IDE for exmaple.

You can docker stop the container. In vscode if you do the open in devcontainer it will simply start the container again, without any rebuilding.

As to your other things, yes if it gets interrupted during the execution of the postCreateCommand.sh you might end up with a half-provisioned kindev. If it gets interrupted, you can do cd .kind and then make vshnall. It should then behave like normal kindev and continue where it left of. Or run the postCreateCommand.sh again by calling .devcontainer/postCreateCommand.sh.

Also, you don't have to rebuild the whole thing if you change your dotfiles. The dotfiles are stored in ~/dotfiles and are a simple git repo. So if you change your dotfiles, you can just do something like this:

~/dotfiles
git pull
./install.sh

And your new things will be applied.

Rebuilding is only really required if something fundamentally changes in the Dockerfile. Or if you break the container somehow :D