Stuck on docker_image.main
After installing code inside docker and creating a docker template and then a workspace it is stuck seemingly infinitely on docker_image.main: Still creating...
Eventually it fails because ====================
Coder: Build has been detected as hung for 5 minutes and will be terminated.
====================
5 Replies
<#1227092580047654973>
Category
Help needed
Product
Coder OSS (v2)
Platform
Linux
Logs
Please post any relevant logs/error messages.
Planning infrastructure
4 seconds
Initializing the backend...
Initializing provider plugins...
- Finding latest version of coder/coder...
- Finding latest version of kreuzwerker/docker...
- Installing coder/coder v0.20.1...
- Installed coder/coder v0.20.1 (signed by a HashiCorp partner, key ID 93C75807601AA0EC)
- Installing kreuzwerker/docker v3.0.2...
- Installed kreuzwerker/docker v3.0.2 (self-signed, key ID BD080C4571C6104C)
Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html
Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.
Terraform has been successfully initialized!
You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.
If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
Plugin Signing | Terraform | HashiCorp Developer
Plugin Signing | Terraform | HashiCorp Developer
Learn about the types of signatures providers can have on the Terraform Registry.
Terraform 1.6.6
data.coder_provisioner.me: Refreshing...
data.coder_workspace.me: Refreshing...
data.coder_workspace.me: Refresh complete after 0s [id=e6355099-b18e-4175-bdf5-c8c0a2e6b2fe]
data.coder_provisioner.me: Refresh complete after 0s [id=f12881a3-7dda-43ee-881a-57a9f4e9a7b8]
docker_volume.home_volume: Refreshing state... [id=coder-e6355099-b18e-4175-bdf5-c8c0a2e6b2fe-home]
coder_agent.main: Refreshing state... [id=1c8a6f55-28c2-4362-8c82-8b9a94fdef63]
docker_volume.home_volume: Refresh complete [id=coder-e6355099-b18e-4175-bdf5-c8c0a2e6b2fe-home]
coder_agent.main: Refresh complete [id=1c8a6f55-28c2-4362-8c82-8b9a94fdef63]
coder_app.code-server: Refreshing state... [id=bbc771c5-75b4-4485-b9a0-3ac99876a971]
coder_app.code-server: Refresh complete [id=bbc771c5-75b4-4485-b9a0-3ac99876a971]
coder_agent.main: Drift detected (update)
docker_image.main: Plan to create
docker_container.workspace[0]: Plan to create
Plan: 2 to add, 0 to change, 0 to destroy.
Terraform 1.6.6
docker_image.main: Plan to create
docker_container.workspace[0]: Plan to create
docker_image.main: Creating...
docker_image.main: Still creating... [10s elapsed]
docker_image.main: Still creating... [20s elapsed]
docker_image.main: Still creating... [30s elapsed]
docker_image.main: Still creating... [40s elapsed]
docker_image.main: Still creating... [50s elapsed]
docker_image.main: Still creating... [1m0s elapsed]
docker_image.main: Still creating... [1m10s elapsed]
docker_image.main: Still creating... [1m20s elapsed]
docker_image.main: Still creating... [1m30s elapsed]
docker_image.main: Still creating... [1m40s elapsed]
docker_image.main: Still creating... [1m50s elapsed]
docker_image.main: Still creating... [2m0s elapsed]
docker_image.main: Still creating... [2m10s elapsed]
docker_image.main: Still creating... [2m20s elapsed]
docker_image.main: Still creating... [2m30s elapsed]
docker_image.main: Still creating... [2m40s elapsed]
docker_image.main: Still creating... [2m50s elapsed]
I now know what the problem is. The docker network bridge has no internet connection. Does someone know how to fix this?
Do you try to build our docker image with docker build cli to be sure they are no errors in tour dockerfile
hey, would you mind sharing your Dockerfile?
also, as @dakeyras suggested, you should try to build the image with the Docker CLI first to see if it works