-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
yarn run start-console
doesn't work with docker
#60
Comments
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale @gaohoward What OS are you running? Is it Linux? It looks like I haven't tried to run the plugin template with OpenShift Local. We'll need to investigate. cc @jhadvig |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale /assign @jhadvig |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
When I start the console using podman the plugin are loaded and works.
However if I force it to use docker the console gets 'no such host' error.
The following shows the output of
yarn run start-console
:Looks like it has problems accessing api.crc.testing and host.docker.internal from inside the container?
The text was updated successfully, but these errors were encountered: