Skip to content

Conversation

@thienandangthanh
Copy link
Owner

@thienandangthanh thienandangthanh commented Sep 6, 2025

Fix problem that output of devpod can't be parsed after devpod v0.5.29

Cherry-picked commit from amitds1997#204 to test and verify with GitHub Actions.

thienandangthanh and others added 5 commits September 6, 2025 15:20
…issues

- Add Docker container detection using multiple indicators (/.dockerenv,
  $container variable, cgroup checks, mountinfo)
- Automatically override 'binary' install method to 'tarball' when Docker
  is detected to avoid AppImage execution failures
- Implement complete tarball download, extraction and installation workflow
- Add version-aware tarball asset naming (nvim-linux64.tar.gz for <v0.10.4,
  nvim-linux-{arch}.tar.gz for >=v0.10.4)
- Support checksum verification for tarball downloads with version-specific
  handling (direct .sha256sum files for <v0.11.3, GitHub API for >=v0.11.3)
- Handle extraction directory naming differences across Neovim versions
- Preserve existing AppImage functionality for non-containerized environments

Fixes universal AppImage extraction failures in Docker containers affecting
all Neovim versions (v0.9.1-v0.11.3+) due to missing FUSE support and
container runtime limitations.

Resolves: AppImage execution fails with "No such file or directory" in
Docker containers, leaving broken symlinks and unusable Neovim installations
…r_container field

Add is_docker_container=false to expected workspace config in provider test
to match the new field added by Docker container detection functionality.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants