You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bug: Obscure error when using Docker template #1198
Same with this one @ammario With this sprint so packed to get to Beta and that we have a sprint before the switch happens, I am going to align this with the first sprint of community. That does not mean it can't be picked up before that though. Let me know if you still want to inject this into Beta. CC @tjcran
@johnstcn and @mafredri timebox this investigation to see if you can find root cause and get an estimate for points and then we will evaluate if this is still a switch blocker
Paired with @mafredri -- spent a couple hours and was able to partially reproduce the issue, although there have been several improvements since then.
Also noting I am able to run through the docker-local flow on my M1 mac on latest master (using Colima instead of Docker Desktop). So I'm not sure if this can still be called a switch-blocker.
Steps to reproduce
Input invalid Terraform to cause the import job to fail (for example, reference a missing variable or provide an invalid parameter).
Terraform v1.1.9 has some fixes for CLI output (we currently embed 1.1.7).
We didn't have arm64 scripts for coder agent at the time; I believe this might have been the root cause of the missing variable in the terraform input.
job has already been marked as failed doesn't appear to happen any more.
We do now have the Terraform output in the CLI so that at least provides more detail
$ coder templates create
> Create and upload "/tmp/docker-local"? (yes/no)
✔ Queued [28ms]
✔ Setting up [3ms]
✔ Adding README.md... [0ms]
✔ Parse parameters [2ms]
⧗ Detecting persistent resources
Terraform 1.1.7
Error: Unsupported attribute
This object has no argument, nested block, or exported attribute named "init_scripttt". Did you mean "init_script"?
✘ Detecting persistent resources [4694ms]
template import provision for start: recv import provision: plan terraform: exit status 1
Fixes
Improve CLI error message in provisionerd when running import job fails (estimate: 1 point)
Unable to reproduce issue on rPi 3 with latest version (arm64)
Unable to reproduce with auto-installed terraform on version 8661f92 -- coder server --dev fails to start with the error install terraform: unexpected Content-Type: "application/vnd+hashicorp.releases-api.v0+json"
One thing that helps a bit with troubleshooting this kind of problem: the default Docker logging driver deletes logs as soon as a container is deleted. But if you use the journald driver instead, you can view logs even after container deletion, using journalctl -u docker.service.
Reacted by Cian Johnston, Joe Previte and Mathias Fredriksson
Activity
[-]Bug: Obscure error when Docker daemon is off[/-][+]Bug: Obscure error when using Docker template[/+]misskniss commentedon May 5, 2022
Same with this one @ammario With this sprint so packed to get to Beta and that we have a sprint before the switch happens, I am going to align this with the first sprint of community. That does not mean it can't be picked up before that though. Let me know if you still want to inject this into Beta. CC @tjcran
misskniss commentedon May 5, 2022
Hey team! Please add your planning poker estimate with ZenHub @jsjoeio @bpmct
6 remaining items
misskniss commentedon May 10, 2022
Please add your planning poker estimate with ZenHub @kylecarbs
misskniss commentedon May 17, 2022
@johnstcn and @mafredri timebox this investigation to see if you can find root cause and get an estimate for points and then we will evaluate if this is still a
switch blockermisskniss commentedon May 17, 2022
Hey team! Please add your planning poker estimate with ZenHub @johnstcn @mafredri
johnstcn commentedon May 18, 2022
Paired with @mafredri -- spent a couple hours and was able to partially reproduce the issue, although there have been several improvements since then.
Also noting I am able to run through the
docker-localflow on my M1 mac on latest master (using Colima instead of Docker Desktop). So I'm not sure if this can still be called a switch-blocker.Steps to reproduce
arm64scripts for coder agent at the time; I believe this might have been the root cause of the missing variable in the terraform input.job has already been marked as faileddoesn't appear to happen any more.Fixes
Notes
coder server --devfails to start with the errorinstall terraform: unexpected Content-Type: "application/vnd+hashicorp.releases-api.v0+json"CC @tjcran @misskniss
jsjoeio commentedon May 20, 2022
@johnstcn chiming in to see if I can help move this forward. Should we turn your other fixes(first 3) into issues and close this?
johnstcn commentedon May 20, 2022
@jsjoeio I don't think that much overhead is necessary! I was thinking of just attaching PRs to this ticket for each of those.
dwahler commentedon May 24, 2022
One thing that helps a bit with troubleshooting this kind of problem: the default Docker logging driver deletes logs as soon as a container is deleted. But if you use the
journalddriver instead, you can view logs even after container deletion, usingjournalctl -u docker.service.johnstcn commentedon May 25, 2022
Ended up making a separate issue for provisioner job output, as we need to ensure adminstrators can set its verbosity independently #1733
johnstcn commentedon May 27, 2022
Closing this issue out, as: