Skip to content
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

Replace all use of Dockerfile by Containerfile #992

Open
travier opened this issue Sep 7, 2022 · 7 comments
Open

Replace all use of Dockerfile by Containerfile #992

travier opened this issue Sep 7, 2022 · 7 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@travier
Copy link
Member

travier commented Sep 7, 2022

Let's make it explicit that this is not about Docker but about containers.

@Conan-Kudo
Copy link

Conan-Kudo commented Sep 20, 2022

Not that I don't have a problem with this, but has anyone attempted to make Docker/Moby support this filename by default too? Otherwise changing the filename creates a fair bit of annoyance for consuming them.

@travier
Copy link
Member Author

travier commented Sep 20, 2022

This is outside of the scope of this project's issue tracker.

@Conan-Kudo
Copy link

Then let's not bother renaming the files until the issue is resolved where it should be.

@travier
Copy link
Member Author

travier commented Sep 20, 2022

Changing the names that we use here is in scope. Changing the behavior of Docker is something else. We don't ship or use Docker in OCP or OKD.

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 20, 2022
@openshift-bot
Copy link

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 19, 2023
@travier
Copy link
Member Author

travier commented Jan 19, 2023

/remove-lifecycle stale
/lifecycle frozen

@openshift-ci openshift-ci bot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Jan 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

3 participants