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
At the moment, we still require our workflows to invoke docker-up to even use Docker. This removes some of the benefits of having "less" to set-up on the workflow, since you still need to manually invoke docker-up everytime you want to work on a Docker project.
docker-up as much as possible should be invoked in the background instead of requiring the user to do it manually, since it doesn't make sense to call it from CLI when you expect Gitpod to do it for you.
The text was updated successfully, but these errors were encountered:
Thank you for bringing this up. Indeed, this is fixed by #4018 which basically makes docker available in every workspace without having to call docker-up first. You should see this feature land before the end of next week.
Closing this issue for now. If the aforementioned PR does not solve this issue for you, please reopen.
At the moment, we still require our workflows to invoke
docker-up
to even use Docker. This removes some of the benefits of having "less" to set-up on the workflow, since you still need to manually invokedocker-up
everytime you want to work on a Docker project.docker-up
as much as possible should be invoked in the background instead of requiring the user to do it manually, since it doesn't make sense to call it from CLI when you expect Gitpod to do it for you.The text was updated successfully, but these errors were encountered: