AWS linux VM - in `connecting` status
I'm using the AWS Linux example and have run
aws configure on my Coder host, and I see a new VM in my AWS console, but in Coder, the workspace stays in connecting and the icons never show up.
I have tried Coder provider 0.4.6 and 0.4.8 and still no joy. The auth in coder_agent is:
auth = "aws-instance-identity"
Any troubleshooting suggestions?5 Replies
The issues related are about staying in connecting status when the VM is off. That is not my problem.
Issue 3611 filed https://github.com/coder/coder/issues/3611
GitHub
bug: default aws linux vm template stuck in
connecting status · I...This does not appear to be related to #3511 but even so, that looks like it is one of Coder's dogfood instances with metadata which is no what I am using. As a new Coder OSS user, where my ...
@Ben helped me troubleshoot. See temporary solution: use
ubuntu user https://github.com/coder/coder/issues/3611#issuecomment-1221367432GitHub
bug: default aws linux vm template stuck in
connecting status · I...This does not appear to be related to #3511 but even so, that looks like it is one of Coder's dogfood instances with metadata which is no what I am using. As a new Coder OSS user, where my ...
Bug: my user is admin which conflicts with Unix group called admin so user isn’t created. Issue filed
Occurs with Azure VMs too. Solution: have a username other than admin 😛
A fix is in https://github.com/coder/coder/pull/3625
GitHub
fix: use hardcoded "coder" user for AWS and Azure by bpmct · Pull R...
fixes #3611 #3511
@spikecurtis explains the problem well:
Ok, we've chased this down. The issue is when the Coder user is named admin, the cloud-init fails because it tries to create user=admi...