Add podman #155
Add podman #155
Conversation
Import them from Gentoo upstream with adjusted `PYTHON_COMPAT`. Like stated in [1] I used `python3_7` instead of the higher versions. 1: https://kinvolk.io/docs/flatcar-container-linux/latest/reference/developer-guides/sdk-modifying-flatcar/
The tests fail in our case because they try to run gpg-agent:
```
F: mkdir
S: deny
P: /run/user/1000/gnupg/d.ph5m99dhy9r3j8bfqigd5zhz
A: /run/user/1000/gnupg/d.ph5m99dhy9r3j8bfqigd5zhz
R: /run/user/1000/gnupg/d.ph5m99dhy9r3j8bfqigd5zhz
C: gpg-agent --homedir
/build/amd64-usr/var/tmp/portage/app-crypt/gpgme-1.15.1/work/b/tests/json
--use-standard-socket --daemon
F: mkdir
S: deny
P: /run/user/1000/gnupg/d.ph5m99dhy9r3j8bfqigd5zhz
A: /run/user/1000/gnupg/d.ph5m99dhy9r3j8bfqigd5zhz
R: /run/user/1000/gnupg/d.ph5m99dhy9r3j8bfqigd5zhz
C: gpg --batch --no-permission-warning --import
../../tests/gpg/secdemo.asc
F: mkdir
S: deny
P: /run/user/1000/gnupg/d.tsrkj355xodiytsa45prsa8p
A: /run/user/1000/gnupg/d.tsrkj355xodiytsa45prsa8p
R: /run/user/1000/gnupg/d.tsrkj355xodiytsa45prsa8p
C: gpg-connect-agent --no-autostart --dirmngr KILLDIRMNGR
F: mkdir
S: deny
P: /run/user/1000/gnupg/d.tsrkj355xodiytsa45prsa8p
A: /run/user/1000/gnupg/d.tsrkj355xodiytsa45prsa8p
R: /run/user/1000/gnupg/d.tsrkj355xodiytsa45prsa8p
C: gpg-connect-agent -s --no-autostart GETINFO scd_running /if ${! $?}
scd killscd /end
```
At first I wanted to use `RESTRICT="test` to omit them.
But we need to omit the actual run of gnupg too and according to [1]
`RESTRICT` doesn't work on `src_setup()`.
So I figured like this it's the least intrusive change to stay similar
to the gentoo ebuild.
1: https://devmanual.gentoo.org/ebuild-writing/variables/index.html
|
Hi, It's good to try to minimize what we change but I think there will be changes needed and in the end some packages will go to coreos-overlay due to this. The main thing to be adjusted is to move the configuration files either to |
|
It pulls in quite a lot of new packages. As for go-md2man, podman seems to pull in go-md2man as We could either move podman to coreos-overlay for changing it to BDEPEND in its ebuild, or directly contribute to Gentoo to fix the issue. The latter is obviously desirable, but it could take time. gpgme looks like an essential dependency of podman. So for now I just hope we could make some free space in the production image after rkt deprecation. :-) |
|
@jubalh thanks, this was good work but the world has changed and it will be implemented slightly differently (sysext). |
Add podman
Add podman and its dependencies (flatcar/Flatcar#112)
New packages:
Package updates:
New eclass:
I chose to add these to portage-stable instead of coreos-overlay, following the documentation that ebuilds that are imported from Gentoo and have few modifications should be put here.
Modifcations:
pkg_setup()) since this tries to run gpg-agent.PYTHON_COMPATtopython3_7How to use
Both dev-go/go-md2man and app-crypt/gpgme need to be installed in the SDK chroot.
I have the following packages unmasked in
chroot/build/amd64-usr/etc/portage/package.accept_keywords:Do these need to be added to some profile?
For now when emerging podman the following is printed:
As does the upstream Gentoo ebuild. We could add these steps in our ebuild. However I checked a couple of our other ebuilds and couldn't find any that do similar things. So I'm unsure whether this should be left our or whether I need to do this in some other file/script.
Testing done
TODO