Skip to content

bug: default aws linux vm template stuck in connecting status when username is admin #3611

Closed
@sharkymark

Description

@sharkymark

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 organization uses AWS only, I would like to experiment with Coder. I have no interest in trying any of the Docker templates, which may be easy.

The docs lead me down a rabbit hole of do I need to use the AWS provider since you reference all the cloud providers.
https://coder.com/docs/coder-oss/latest/templates/authentication

Then I run coder templates init and see an AWS Linux VM example so create that. I see the AWS provider down the main.tf versus at the top.

I figured out that I need to install the aws CLI on my host running Coder, and then run aws configure. Again, this is not documented. At this point, fingers crossed, I can guess Coder can provision workspaces.

Then I coder templates create the template into Coder, and create a workspace, at which:

  1. Joy, 🥳 I see a VM in my AWS console
  2. Boo, 💩 the Coder workspace UI is stuck in connecting status and the code-server coder_app that I added does not come up.

Coder provider: 0.4.8
Coder version: 0.8.5

There is no documentation on how to troubleshoot things like this. My VM doesn't let me SSH in, so I'm basically in a pickle until an expert helps me out.

image

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions