Does Coder Honor the Devcontainers Spec fully?
Hi Folks, I've been having some difficulties with devcontainers and coder. I've been using devcontainers successfully with GitHub codespaces. Coder picks up the correct image from devcontainer.json but nothing else. I've attached the template's
// Add the IDs of extensions you want installed when the container is created. "extensions": [ "hashicorp.terraform", "ms-kubernetes-tools.vscode-kubernetes-tools" ] } }, "hostRequirements": { "cpus": 4, "memory": "16gb", "storage": "32gb" } }
main.tf
file and the logs. And below is the devcontainers.json
file. Any suggestions?
{
"image": "mcr.microsoft.com/devcontainers/universal:2-linux",
"postCreateCommand": "/bin/bash -i -c .devcontainer/startup_script.sh",
"customizations": {
// Configure properties specific to VS Code.
"vscode": {// Add the IDs of extensions you want installed when the container is created. "extensions": [ "hashicorp.terraform", "ms-kubernetes-tools.vscode-kubernetes-tools" ] } }, "hostRequirements": { "cpus": 4, "memory": "16gb", "storage": "32gb" } }
4 Replies
hey @SamG,
is this the full workspace log?
oh sorry, Discord ellipsized it
GitHub
GitHub - coder/envbox: envbox is an image that enables creating non...
envbox is an image that enables creating non-privileged containers capable of running system-level software (e.g. dockerd, systemd, etc) in Kubernetes. - coder/envbox
what's wrong? it seems like the logs are okay
do you maybe have an error message that you can send/screenshot ?
fyi: Git is part of the built-in icons, so you can just do this
for the following part, you might consider using the Git Config module.
also, some of your resources refer to a
var.namespace
variable that isn't defined