Skip to content
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

Improve default experience with Devcontainers #203

Open
zroug opened this issue Feb 5, 2021 · 3 comments
Open

Improve default experience with Devcontainers #203

zroug opened this issue Feb 5, 2021 · 3 comments

Comments

@zroug
Copy link

zroug commented Feb 5, 2021

Using Devcontainers is a nice way to develop when there are issues with VSCode being sandboxed. Getting Devcontainers to work from the VSCode Flatpak is easy. Just create a simple wrapper script

#!/bin/sh
exec flatpak-spawn --host docker "$@"

and point the Devcontainer extension to it.

I suggest to ship this wrapper with the VSCode Flatpak, so that the Devcontainer extension works out of the box. Having the same wrapper for Podman might be a good idea too. Another option would be to describe this workaround in flatpak-warning.txt.

@duesenfranz
Copy link

Currently, this requires the flatpak to be run with --filesystem=/tmp, as vs code puts a Dockerfile into /temp/vsch and then points docker to it.

@FilBot3
Copy link

FilBot3 commented Sep 8, 2021

Is this related to Issue #55 ?

@FilBot3
Copy link

FilBot3 commented Sep 8, 2021

See my Comment here: Issue #55 (comment)

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

No branches or pull requests

3 participants