Fedora Silverblue + podman + DevPod does not work

[twaananen]

Fedora Silverblue + podman + DevPod does not work

[m2Giles]

I also ran into this using the appimage.

I was able to startup a container using podman with a native package, but it would fail open in vscode. This behaviour would continue when using docker as well. The error being ENAMETOOLONG. However, it would open in the vscode browser session. I'm also on an rpm-ostree desktop as well.

[jpotts10]

I also ran into this using the appimage.

I was able to startup a container using podman with a native package, but it would fail open in vscode. This behaviour would continue when using docker as well. The error being ENAMETOOLONG. However, it would open in the vscode browser session. I'm also on an rpm-ostree desktop as well.

Just wanted to comment saying I also experienced this issue on Bluefin-dx GTS on a fresh install in a VM two days ago.

[zentasumu]

Issue is still present.

AppImage version 0.5.18, running on Fedora 40 Atomic Sway (Sericea).

[pascalbreuninger]

@m2Giles we haven't released a new version yet, it should work if you run from source. We'll cut one towards the end of the week

[3timeslazy]

For everyone struggling with selinux related "Permission denied" error, try adding the following in your devcontainer.json

{
    // some fields

    "workspaceMount": "",
    "workspaceFolder": "/workspaces/${localWorkspaceFolderBasename}",
    "runArgs": [
        // other args
        "--volume=${localWorkspaceFolder}:/workspaces/${localWorkspaceFolderBasename}:Z"
    ]
}

This will make devpod (and any other devcontainer implementation, I guess) to mount everything with :Z suffix which will relabel the files

[89luca89]

Thanks for reporting @twaananen will investigate 👍

[m2Giles]

Still seeing this issue with the appimage. The image below just keeps looping. It works with a locally installed version of devpod.

I'm currently using version v0.5.5 and still get this error.

I'm on Bazzite as well and also trying to use Podman.

I get the exact same error as @twaananen.

[MileaRobertStefan]

v0.5.5

12:56:39 info main.main
12:56:39 info   D:/a/devpod/devpod/main.go:8
12:56:39 info runtime.main
12:56:39 info   C:/hostedtoolcache/windows/go/1.21.8/x64/src/runtime/proc.go:267
12:56:39 info runtime.goexit
12:56:39 info   C:/hostedtoolcache/windows/go/1.21.8/x64/src/runtime/asm_amd64.s:1650`

devcontainer.json:

// For format details, see https://aka.ms/devcontainer.json. For config options, see the README at:
// https://github.com/microsoft/vscode-dev-containers/tree/v0.231.5/containers/elixir-phoenix-pgitostgres
{
  "name": "App Elixir",

  "service": "app",

  // "build": {
  //   "dockerfile": "../Dockerfile",
  //   "context": ".."
  // },

  "dockerComposeFile": "../docker-compose.yml",
  "shutdownAction": "stopCompose",

  "workspaceFolder": "/app",

  "features": {
    // "ghcr.io/devcontainers/features/docker-in-docker:2": [],
    // "ghcr.io/devcontainers/features/go:1": [],
    "ghcr.io/devcontainers-contrib/features/elixir-asdf:2": [],
    "ghcr.io/devcontainers/features/github-cli:1": [],
    "ghcr.io/devcontainers/features/sshd:1": []
  },

  "customizations": {
    "vscode": {
      "settings": {
        "terminal.integrated.defaultProfile.linux": "bash"
      },
      "extensions": [
        "streetsidesoftware.code-spell-checker",
        "GitHub.copilot",
        "GitHub.copilot-chat",
        "github.vscode-pull-request-github",
        "jakebecker.elixir-ls",
        "phoenixframework.phoenix",
        "redhat.vscode-yaml"
      ]
    }
  },

  "postCreateCommand": "",

  // Use 'forwardPorts' to make a list of ports inside the container available locally.
  // This can be used to network with other containers or with the host.
  "forwardPorts": [4000, 8080, 80]

  // Use 'postCreateCommand' to run commands after the container is created.
  // "postCreateCommand": "mix deps.get",

  // "remoteUser": "vscode"
}

I'm trying to setup an elixir environment.

[Pra3t0r5]

Im having the same issue on Bluefin (Fedora Silverblue)

[midoriiro]

Still present in 0.5.19 on SilverBlue. I did not encountered this issue on Sericea few day ago on 0.5.18 and 0.5.19. Until this is fixed, a workaround can set Docker binary in your Docker provider as podman-remote. Since is not depend on conmon.so that should do the trick. Not ideal but is work fine.