Hi, is there a guide/resource on how to
Hi, is there a guide/resource on how to make devpod/devcontainers work on silverblue/ublue/bazzite?
17 Replies
I have installed the AppImage for DevPod, I have podman and podman-compose on my system and I have configured a docker provider with: docker host = /run/user/1000/podman/podman.sock and docker path = /usr/bin/podman
Can't get any of the example workspaces to work.
podman has SELinux enabled by default and works a little different from docker.
In the .devcontainer.json you will need to add the --userns=keep-id and --security-opt label=disable (if using a directory in HOME)
If you are using the a user other than root you also will need to specify the HOME directory for the user. See the bluefin .devcontainer which has an example that works with podman.
https://github.com/ublue-os/bluefin/blob/main/.devcontainer/devcontainer.json
Hmm. I tried that devcontainer file from bluefin and it fails in devpod in the exact same manner.
[23:12:31] info Error: creating container storage: creating an ID-mapped copy of layer "b09d5ecb11b82813ebd151d3e3f7410fbcfa81a7b7bda05eaf29bfdc18ac7d0a": storage-chown-by-maps: /tmp/.mount_gearlegXxe21/usr/lib/libselinux.so.1: no version information available (required by /lib64/libsubid.so.4) [23:12:31] info storage-chown-by-maps: /tmp/.mount_gearlegXxe21/usr/lib/libselinux.so.1: no version information available (required by /lib64/libsemanage.so.2) [23:12:31] info exit status 125
This is the only thing labeled error in the logs. I don't know how relevan it is.I've been able to confirm that issue occurs with Devpod and the app image.
Good to hear it is not just me. I haven't been able to debug this. Do you think this could be addressed by ourselves or should I file a bug report to devpod?
I think this is Devpod + podman related right now.
I have Devpod on my laptop but I use that with docker. I'll see if I can swap over to podman and the issue persists.
on my laptop I was able to get it to work with the web version of vscode.
I removed setting the docker host. I only have podman configured as the docker binary path.
When attempting to connect with layered vscode I get an error with SSH saying the name is too long or something to that effect. Basically the name is somehow to long. However, this can be opened when using browser based vscode
I changed the container to ubuntu. This devpod is layered and I'm on bluefin and not bazzite
Pretty sure I saw your issue on github and added that I saw it as well along with the note that it is also broken with a native pacakge
Yeah, I just added the issue there. Thanks
I tried doing the setup you described, no luck
- web vscode
- only podman binary path
- ubuntu as base
same selinux indicated issue?
I currently have selinux on permissive
That must be something with the appimage
What version is your layered package?
0.5.4
you can grab from here
https://copr.fedorainfracloud.org/coprs/ublue-os/staging/
Thanks I'll try layering it tomorrow. I'm no really familiar with copr, but I'll check it out.
just add teh repo file to
/etc/yum.repos.d and you can do an rpm-ostree install devpod. For local containers, the built-in vscode devcontainers extension works fine and I've been using with both distrobox and devcontainersgreat thanks!