-
Notifications
You must be signed in to change notification settings - Fork 485
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build with Containerfile instead of Dockerfile #167
Comments
I would also appreciate support for |
It's strange it isn't a thing yet. I say it has to be of a higher priority since Podman itself uses "Containerfile" just fine |
please test |
Writing
It worked perfectly fine with docker-compose wired to podman docker-compose.yml:
|
this does not seem to be my code, the raise statement in my code is around line 1343 |
Oh, turns out this is because pip features an old release. See #338 |
Would you please confirm if the latest devel branch fix it?
…On Thu, Nov 11, 2021, 10:08 PM Maksym Hazevych ***@***.***> wrote:
Oh, turns out this is because pip features an old release. See #338
<#338>
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#167 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKAPK6CLENZJ4EGRCUBD6DULQPDZANCNFSM4MZOIWOQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Hi, sorry it took so long. The devel version works just fine with both |
I just tried to create a stack which uses a file named
Containerfile
instead ofDockerfile
, which apparently does not work.Is it possible to support the tool agnostic
Containerfile
as filename?On a related note: why not use
container-compose.yaml
as well? :)The text was updated successfully, but these errors were encountered: