Skip to content

Detect Podman containers in server mode - #116

Open
Landrash wants to merge 1 commit into
TechJeeper:mainfrom
Landrash:fix/podman-container-detection
Open

Landrash wants to merge 1 commit into
TechJeeper:mainfrom
Landrash:fix/podman-container-detection

Conversation

@Landrash

@Landrash Landrash commented Oct 17, 2026 •

Copy link
Copy Markdown

isDockerContainer() only checks /.dockerenv and "docker" in /proc/self/cgroup.
Podman creates neither; it creates /run/.containerenv. Under Podman, server mode therefore applies the Windows UNC-only rule and rejects every STL_HOME scan with "Server mode requires UNC paths".

This adds the /run/.containerenv check in main.js and scan-worker.js. The "requires UNC paths" startup line now only prints when that rule applies.

Tested with the 3.0.0 image under rootless Podman, with the patched files bind-mounted over /app: before, the scan fails with the UNC error; after, it indexes models.

Current workaround for Podman users: -v /dev/null:/.dockerenv:ro.

Created with the help from [Claude Code]

isDockerContainer() only checked /.dockerenv and "docker" in
/proc/self/cgroup. Podman creates neither (it creates /run/.containerenv),
so under Podman server mode applied the Windows UNC-only rule and rejected
every STL_HOME scan. Also check /run/.containerenv, and only print the
"requires UNC paths" startup line when that rule applies.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Landrash
Landrash force-pushed the fix/podman-container-detection branch from ebf1546 to 3206e9d Compare October 17, 2026 14:10
@Landrash
Landrash marked this pull request as ready for review October 17, 2026 14:28
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

Successfully merging this pull request may close these issues.

1 participant