Bug 1944161
| Summary: | Podman missing required dependency | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | james <jamesstewartmiller> |
| Component: | IoT | Assignee: | Peter Robinson <pbrobinson> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 34 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | aarch64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-03-31 12:48:54 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
james
2021-03-29 12:49:26 UTC
You've already filed a bug report here: https://pagure.io/fedora-iot/issue/45 How many bug reports do you think we need for the same problem? as many as it takes to get heard. There are few responses, if any, to the bugs listed at pagure, and I wasn't even sure if it was still maintained, judging by the lack of responses. The issue I have reported is a critical issue for me. I have a server that should be live right now, but the only way to run it is using the downgraded version of podman which is insecure. I don't understand why containers-common should have the wrong version listed, I thought there would be builds at koji that I could simply access, but it seems there is little aarch64 support. However, like I say, I am relying on that aarch build, or I am going to have to use the insecure version of podman. A new version of podman v 3.1 has been released, yesterday. Can we expect to see it and it related packages in the IOT repo soon? (In reply to james from comment #2) > as many as it takes to get heard. There are few responses, if any, to the > bugs listed at pagure, and I wasn't even sure if it was still maintained, > judging by the lack of responses. They don't have responses when there's not a need, doesn't mean they're not monitored (In reply to james from comment #3) > A new version of podman v 3.1 has been released, yesterday. Can we expect > to see it and it related packages in the IOT repo soon? It will be there when it ends up stable in the associated Fedora release as per the documentation. (In reply to james from comment #0) > Description of problem: > I have to use rpm-ostree replace command to replace the bundled-with-base > podman version 3.0.1, as that version doesn't accept connections for > containers inside pods (github issue 9532) > https://github.com/containers/podman/issues/9532. > However, when I try and use the command 'rpm-ostree override replace > https://koji.fedoraproject.org/koji/buildinfo?buildID=1720774' rpm-ostree > complains that it can't find a dependency 'containers-common' of the correct > version. > The exact error is: > ``` > error: Could not depsolve transaction; 2 problems detected: > Problem 1: cannot install both containers-common-4:1-13.fc34.noarch and > containers-common-1:1.2.1-28.dev.git1b813f8.fc34.aarch64 > - package podman-2:3.1.0-0.1.rc1.fc33.aarch64 requires containers-common > >= 4:1-4, but none of the providers can be installed > - conflicting requests > Problem 2: package skopeo-1:1.2.1-28.dev.git1b813f8.fc34.aarch64 requires > containers-common = 1:1.2.1-28.dev.git1b813f8.fc34, but none of the > providers can be installed > - cannot install both containers-common-4:1-13.fc34.noarch and > containers-common-1:1.2.1-28.dev.git1b813f8.fc34.aarch64 > - cannot install both > containers-common-1:1.2.1-28.dev.git1b813f8.fc34.aarch64 and > containers-common-4:1-13.fc34.noarch > - package podman-2:3.1.0-0.1.rc1.fc33.aarch64 requires containers-common > >= 4:1-4, but none of the providers can be installed > - package podman-plugins-2:3.1.0-0.1.rc1.fc33.aarch64 requires podman = > 2:3.1.0-0.1.rc1.fc33, but none of the providers can be installed > - conflicting requests > ``` > However, on my dev machine I am running fedora silverblue, and can install > the override with no issues. I have checked on Koji, and there is no > containers-common version 4:1-13, so I wonder if there is a typo in a > manifest file somewhere. Surely, though, if I can pin the version on > silverblue, I should be able to on IOT. I guess there is no > containers-common for aarch64, assuming it is not a typo. > > Version-Release number of selected component (if applicable): > Fedora 34 Beta IOT aarch64 - - Fedora-IoT-34-20210314.0.aarch64.raw.xz > > How reproducible: > Install aarch64 IOT, run following command: > rpm-ostree override replace > https://koji.fedoraproject.org/koji/buildinfo?buildID=1720774 > see error output reproduced aboe > Steps to Reproduce: > > 1. install aarch64 IOT fedora 34 beta > > 2. run the following command 'rpm-ostree override replace > https://koji.fedoraproject.org/koji/buildinfo?buildID=1720774' > > 3. see output errors (reproduced above) This is because either the dependencies aren't pushed as updates and available in repos or you haven't provided a repo with them in. |