Skip to content

[Bug]: VSCodium Flatpak can't use devpod-cli #761

@wallzero

Description

@wallzero

Before submitting

  • I have searched existing issues to confirm this is not a duplicate
  • I am running the latest version of DevPod

What happened?

VSCodium Flatpak and the DevPod container extension are unable to start devpod.

What did you expect to happen instead?

I expected VSCodium to start devpod to create and launch my dev container.

This setup is working with loft-sh devpod but not this fork.

Steps to reproduce

  1. Install Flatpak Devpod fork
  2. Install Flatpak VSCodium
  3. In VSCode install DevPod Containers](https://github.com/3timeslazy/vscodium-devpodcontainers) extension
  4. In VSCodium settings.json add "remote.devpodcontainers.devpodCommand": "flatpak-spawn --host devpod" so the extension can launch DevPod from within Flatpak

devcontainer.json

{
  "name": "Node.js & TypeScript",
  "image": "mcr.microsoft.com/devcontainers/typescript-node:4-24-trixie"
}

Error output / logs

bwrap: execvp devpod-cli: No such file or directory

How often does this happen?

Every time

Operating system

Linux

Linux distribution (if applicable)

Fedora Kinoite

Architecture

AMD64

Desktop app or CLI?

CLI only

DevPod version

v0.24.0

DevPod provider

Docker

Provider version

v0.0.1

Screenshots

No response

Anything else?

Possibly related to #437

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions