@runlevel5 the ppc64le environment itself seems to not be setup correctly, so we just can't build any packages there. Last time I checked, there was some kernel issues and those were low on the priority list for the admins. So, there's not much we can do.
Sorry, I wasn't specific enough (edited already), I was refering to the podman builds. These are marked as "disabled" and there are indeed no builds for podman 3.1 in the repository.
The support matrix grew too big to keep up with all the packaging work. Especially older distros are challenging (e.g., old kernels, old libraries, etc.).
Any chance apparmor will be enabled at some point? From my understanding containers-common has a application upstream that outputs the required default apparmor profile.
@sagrunert, @vrothberg Dan Walsh mentioned you both would be the right people to ask about apparmor. Could you PTAL and let me know what's to be done here?
In addition to apparmor buildtag, do I need to change anything in containers.conf . I see apparmor_profile = "container-default" in containers.conf. Does that need to be uncommented, or is that assumed by default, or anything else?
Hi, well in particular running podman containers with AA enabled, and I'm personally using Ubuntu 20.04. If you mean which tool generates AppArmour profiles I was on about this: https://github.com/containers/common/tree/main/pkg/apparmor. Warning not a dev only had a quick skim :)
Podman on Ubuntu 20.04 builds with the apparmor tag. Can you please open an issue within the podman repository containing the requested outputs there? I think it would be better to track the issue there if there is some.
Excuse my ignorance but I'm not that familiar with OBS. Where exactly should I open a bug report?
EDIT: Never mind realised you meant containers/podman on GH.
Hi, the cri-o parts and its dependencies are still active, but buildah and podman will likely not be updated here anymore because 22.04 LTS should be released in 2 months and it will have buildah by default.
Do you consider providing updates for at least 18.04 and 20.04? These versions are still supported and having fresh container tools would be very helpful. Docker maintains its repo for these and other distributions. I wouldn't want to migrate to docker back because podman and buildah stopped receiving updates.
Not sure if I missed it, but has podman 3.x been removed? This used to be the only place it was available for CentOS 7, and now I no longer see it here. Thanks!
I am using Ubuntu 22.04, and it appears the Release key file in the repo server itself is outdated compared to the one on file with Open Build Service here, I was getting errors due to the key expiring on 12/6/22 and so I just added the key from Open Build Service instead and now the errors went away.
When trying to refresh keys from the ubuntu keyserver and various others it told me there was no change to the key that had expired, but the one on the build service is the correct one, I guess it just hasn't gotten synced yet?
Comments 27
runlevel5 wrote over 1 year ago
HI team
I would like to ask why there is no build for ppc64le on xUbuntu_20.04 and 20.10?
Thanks
Trung
haircommander wrote over 1 year ago
I've attempted to enable it!
lsm5 wrote over 1 year ago
@runlevel5 the ppc64le environment itself seems to not be setup correctly, so we just can't build any packages there. Last time I checked, there was some kernel issues and those were low on the priority list for the admins. So, there's not much we can do.
_nobody_ wrote over 1 year ago
This comment has been deleted
Delete comment?
Please confirm deletion of comment
RBrownSUSE wrote over 1 year ago
I don't see any evidence that builds for Debian_10 have been disabled..how/where did you discover this?
rsommer wrote over 1 year ago
Sorry, I wasn't specific enough (edited already), I was refering to the podman builds. These are marked as "disabled" and there are indeed no builds for podman 3.1 in the repository.
vrothberg wrote over 1 year ago
Older distros are not receiving packages anymore (see https://podman.io/blogs/2021/03/02/podman-support-for-older-distros.html).
The support matrix grew too big to keep up with all the packaging work. Especially older distros are challenging (e.g., old kernels, old libraries, etc.).
DazEErR wrote over 1 year ago
Any chance apparmor will be enabled at some point? From my understanding containers-common has a application upstream that outputs the required default apparmor profile.
lsm5 wrote over 1 year ago
@sagrunert, @vrothberg Dan Walsh mentioned you both would be the right people to ask about apparmor. Could you PTAL and let me know what's to be done here?
sagrunert wrote over 1 year ago
I don't see why not, we may just add libapparmor as (optional) dependency and add the corresponding build tag if available, right? :)
lsm5 wrote over 1 year ago
In addition to apparmor buildtag, do I need to change anything in containers.conf . I see apparmor_profile = "container-default" in containers.conf. Does that need to be uncommented, or is that assumed by default, or anything else?
lsm5 wrote over 1 year ago
I see that I have added the apparmor buildtag to podman build rules already. So, I'm guessing there's something else that we need to include?
sagrunert wrote over 1 year ago
I assume we're talking about Podman. About which distribution are we talking?
lsm5 wrote over 1 year ago
@DazEErR are you talking about any tool in particular? podman / buildah / cri-o? Also, any Ubuntu version in particular?
DazEErR wrote over 1 year ago
Hi, well in particular running podman containers with AA enabled, and I'm personally using Ubuntu 20.04. If you mean which tool generates AppArmour profiles I was on about this: https://github.com/containers/common/tree/main/pkg/apparmor. Warning not a dev only had a quick skim :)
lsm5 wrote over 1 year ago
@sagrunert ^
sagrunert wrote over 1 year ago
Podman on Ubuntu 20.04 builds with the apparmor tag. Can you please open an issue within the podman repository containing the requested outputs there? I think it would be better to track the issue there if there is some.
DazEErR wrote over 1 year ago
Excuse my ignorance but I'm not that familiar with OBS. Where exactly should I open a bug report? EDIT: Never mind realised you meant containers/podman on GH.
srbala wrote about 1 year ago
@lsm5 Please update podman to version
3.4.0lsm5 wrote about 1 year ago
See: https://build.opensuse.org/project/show/devel:kubic:libcontainers#comment-1529213
walddys wrote 12 months ago
cri-o-runc is removed or included on the compile of the main package? because this last one is not on the repo.
quarck wrote 10 months ago
Is this project still active? Ubuntu 20.04 hasn't seen updates for half a year already.
lsm5 wrote 10 months ago
Hi, the cri-o parts and its dependencies are still active, but buildah and podman will likely not be updated here anymore because 22.04 LTS should be released in 2 months and it will have buildah by default.
quarck wrote 10 months ago
Do you consider providing updates for at least 18.04 and 20.04? These versions are still supported and having fresh container tools would be very helpful. Docker maintains its repo for these and other distributions. I wouldn't want to migrate to docker back because podman and buildah stopped receiving updates.
bgz wrote 7 months ago
Not sure if I missed it, but has podman 3.x been removed? This used to be the only place it was available for CentOS 7, and now I no longer see it here. Thanks!
luneo7 wrote 7 months ago
Buildah is broken on Debian 10... we are getting: buildah : Depends: crun (>= 100:0.18-3) but it is not going to be installed
The avaiable crun version is 100:0.18-2 ....
therealboratsagdiyev wrote 1 day ago
I am using Ubuntu 22.04, and it appears the Release key file in the repo server itself is outdated compared to the one on file with Open Build Service here, I was getting errors due to the key expiring on 12/6/22 and so I just added the key from Open Build Service instead and now the errors went away.
When trying to refresh keys from the ubuntu keyserver and various others it told me there was no change to the key that had expired, but the one on the build service is the correct one, I guess it just hasn't gotten synced yet?