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
This approach is brittle because it strongly couples the template with the Access URL. In this example, if the Access URL is 127.0.0.1 and not localhost, the agent will never start.
@kylecarbs suggested we add a host attribute the coder_provider block that would contain the host.docker.internal isntead.
The text was updated successfully, but these errors were encountered:
@kylecarbs I think this one is pretty high priority, as it tripped up Elliot during his attempt to try Coder, and half of our example templates fail depending on whether someone uses localhost or 127.0.0.1.
This issue is becoming stale. In order to keep the tracker readable and actionable, I'm going close to this issue in 7 days if there isn't more activity.
By default, Docker containers are on their own network and access the host via
host.docker.internal
.The existing (and non-obvious) workaround is to replace the Access URL in the
init_script
. See below:This approach is brittle because it strongly couples the template with the Access URL. In this example, if the Access URL is
127.0.0.1
and notlocalhost
, the agent will never start.@kylecarbs suggested we add a
host
attribute thecoder_provider
block that would contain thehost.docker.internal
isntead.The text was updated successfully, but these errors were encountered: