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.

Sign up for GitHub

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

Jump to bottom

Make compliant the build scripts with podman #15558

Open
benoitf opened this issue Dec 23, 2019 · 8 comments
Open

Make compliant the build scripts with podman #15558

benoitf opened this issue Dec 23, 2019 · 8 comments
Labels
area/ci CI build and releases, PR testing, & whitelabel/productization issues kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P2 Has a minor but important impact to the usage or development of the system.

Comments

@benoitf
Copy link
Contributor

benoitf commented Dec 23, 2019

Is your task related to a problem? Please describe.

podman is an alternative of docker tools
In almost all docker scripts, docker is used in command line
It would be great that it could handle both tools so people could have only podman installed.

Describe the solution you'd like

build scripts could detect automatically if one the tool is installed and/or use a flag to select which tool to use.

Describe alternatives you've considered

N/A

Additional context

https://podman.io/
@benoitf benoitf added the kind/task Internal things, technical debt, and to-do tasks to be performed. label Dec 23, 2019
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Dec 23, 2019
@ibuziuk ibuziuk added severity/P2 Has a minor but important impact to the usage or development of the system. area/productization and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Dec 23, 2019
@ibuziuk
Copy link
Member

ibuziuk commented Dec 23, 2019

@benoitf is productization the right team for this task ?

@benoitf
Copy link
Contributor Author

benoitf commented Dec 23, 2019

@ibuziuk I don't know if it's a cross-team effort or not so yeah let's leave productization for now

@che-bot
Copy link
Contributor

che-bot commented Jul 6, 2020

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

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

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 6, 2020
@che-bot che-bot closed this as completed Jul 27, 2020
@benoitf benoitf added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 27, 2020
@benoitf benoitf reopened this Jul 27, 2020
@nickboldt
Copy link
Contributor

In almost all docker scripts, docker is used in command line

This needs to be an epic since it spans more than a dozen repos. @benoitf could you list all the repos that need updating to support podman?

Or, rather than tackling this huge ask as a single job, maybe we only care about podman in specific places? Have you hit a docker-not-podman issue in a specific build?

@nickboldt nickboldt removed the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Aug 5, 2020
@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 4, 2021
@che-bot
Copy link
Contributor

che-bot commented Feb 4, 2021

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

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

Moderators: Add lifecycle/frozen label to avoid stale mode.

@ericwill ericwill added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 4, 2021
@ericwill
Copy link
Contributor

ericwill commented Feb 4, 2021

Plugin and devfile registries are done.

@nickboldt nickboldt added area/ci CI build and releases, PR testing, & whitelabel/productization issues and removed team/productization labels Apr 6, 2021
@nickboldt
Copy link
Contributor

nickboldt commented Sep 28, 2021 •
edited
Loading

Projects which now try to use podman as the default (and sometimes fall back to docker if podman not found):

  • configbump
  • che-theia
  • che-release
  • che-docs
  • devfile and plugin registries

@nickboldt
Copy link
Contributor

Projects which still use docker as the primary or explicitl run docker instead of podman:

  • redhat-developer/kubernetes-image-puller
  • jetbrains-editor-images
  • devworkspace-operator
  • che-server
  • eclipse/che
  • che-plugin-broker
  • che-operator
  • che-machine-exec
  • che-jwtproxy
  • chectl

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/ci CI build and releases, PR testing, & whitelabel/productization issues kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@nickboldt @benoitf @l0rd @ibuziuk @ericwill @che-bot