Skip to content

Conversation

meysholdt
Copy link
Member

With this, docker build and docker run will just work in a fresh workspace.

@meysholdt meysholdt changed the title Lauch Dockerd when opening a Gitpod Workspace Lauch Dockerd when opening a Gitpod Workspace on this Repo Dec 1, 2020
@@ -34,6 +34,15 @@ tasks:
- name: Go
init: leeway exec --filter-type go -v -- go get -v ./...
openMode: split-right
- name: Docker
command: |
if [ -x "$(which docker-up)" ]
Copy link
Contributor

@csweichel csweichel Dec 2, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had a bit more of a think about this. While it's true that docker-up is only in the path if feature preview is enabled, that's because feature preview also enables registry-facade. Hence which docker-up is more of a signal for registry facade rather than user namespaces.
Also, in gitpod-io it's likely to have docker-up in the path even without registry-facade due to the go get ... in components/docker-up.

Instead you could check if sudo works, e.g.

if [ sudo true &>/dev/null ]; then
  sudo docker-up
else
  echo "Enable 'Feature Preview' in your Gitpod profile for Docker support."
fi

Base automatically changed from master to main February 23, 2021 18:09
@csweichel
Copy link
Contributor

superseded by #4018

@csweichel csweichel closed this Apr 21, 2021
@AlexTugarev AlexTugarev deleted the me/docker-gitpodyaml branch March 15, 2022 14:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants