Skip to content

Conversation

metroite
Copy link

@metroite metroite commented Aug 12, 2025

Link to docker-compose spec.

See minimal example (works with docker compose, not with podman).

This error occurs when trying to run any podman-compose.yml with a build context: and dockerfile: directive:

Error: no Containerfile or Dockerfile specified or found in context directory, C:/path/to/service/context/hello: The system cannot find the file specified.
Error: executing podman-compose build hello: exit status 125

There is a line in is_context_git_url() which checks for a : in the context path. As Windows uses : to seperate drives, this results in a bad assertion of every Windows path as a git context.

@metroite metroite changed the title [READ WARNING BEFORE MERGE] fix compose not recognizing custom containerfile when in a git context fix compose not recognizing custom containerfile when in a git context (windows exclusive bug only I think?) Aug 13, 2025
@metroite metroite changed the title fix compose not recognizing custom containerfile when in a git context (windows exclusive bug only I think?) fix not recognizing custom containerfile due to the Windows path (C:/soome/path) being misinterpreted as a git context Aug 13, 2025
@metroite metroite force-pushed the main branch 2 times, most recently from b2e2526 to 3145b02 Compare August 13, 2025 00:36
@metroite metroite changed the title fix not recognizing custom containerfile due to the Windows path (C:/soome/path) being misinterpreted as a git context fix failed recognition of custom containerfile due to Windows paths (e.g C:\some\path) being misinterpreted as git urls Aug 13, 2025
@p12tic
Copy link
Collaborator

p12tic commented Aug 21, 2025

@metroite Seems that the PR does not contain any changes.

…eing misinterpreted as git urls

Signed-off-by: Metroite <22453965+Metroite@users.noreply.github.com>
@metroite metroite force-pushed the main branch 2 times, most recently from d5be817 to cdf553f Compare August 22, 2025 23:29
@metroite
Copy link
Author

@metroite Seems that the PR does not contain any changes.

Thank you. I don't know how that happened, but thats probably due to the now roughly 50 force pushes for 3 lines of code. LGTM

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.

2 participants