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

Docker API compatibility and Nomad #8235

Closed
mskarbek opened this issue Nov 3, 2020 · 6 comments
Closed

Docker API compatibility and Nomad #8235

mskarbek opened this issue Nov 3, 2020 · 6 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@mskarbek
Copy link

mskarbek commented Nov 3, 2020

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind feature

Description

@baude, so following today's community meeting I've checked 2.1.1-12.fc33 and 2.2.0-0.39.dev.git287edd4.fc34 compatibility with Nomad. 2.1.1 fails the same way but, as it was suggested during the meeting, something relatively fresh could work, and indeed 2.2.0 dev works. Nomad was able to spawn containers, exec into them - basic stuff. Ofc this needs more testing but is promising. Now, the real question - is this level of compatibility can be provided by RHEL 8.3 with 2.0 in AppStream, and can I already fill the Bugzilla report for that? ;)

@openshift-ci-robot openshift-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Nov 3, 2020
@baude
Copy link
Member

baude commented Nov 3, 2020

i cannot make promises on RHEL commitments here. if you want to have that conversation we could discuss it in a bugzilla I suppose. more importantly, im glad it now works!

@mskarbek
Copy link
Author

mskarbek commented Nov 3, 2020

Ok, so I'm closing this and starting the Bugzilla thread.

@mskarbek mskarbek closed this as completed Nov 3, 2020
@rhatdan
Copy link
Member

rhatdan commented Nov 3, 2020

The first chance you would get podman-2.2 would be in RHEL8.3.1 which comes out in February. If we move to that. RHEL8.4 in May will be podman 3.0.

@mheon
Copy link
Member

mheon commented Nov 3, 2020

8.3.1 is already fixed on 2.1.1 - so it's probably missing things that he needs, if he tested with builds of master

@mskarbek
Copy link
Author

mskarbek commented Nov 4, 2020

@mheon so you are saying that improvements in the API layer compatibility are considered features not fixes and will be released with new versions? That would mean I have to wait for 8.4. Slightly inconvenient, we already waited for 8.3 and 2.0 specifically for Docker API. Ok, we will have to deal with what we have. :)

@rhatdan
Copy link
Member

rhatdan commented Nov 4, 2020

@mskarbek The way RHEL Releases, we have to have code ready a long time before release. So this is more about where the code is during the development phase when we lock in a particular version. In the case of serious bugs like CVEs or crashes we will force an update but otherwise we wait until the next release.

@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 22, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/feature Categorizes issue or PR as related to a new feature. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

No branches or pull requests

5 participants