Use complete Ubuntu release + update base images#34
Use complete Ubuntu release + update base images#34mergify[bot] merged 5 commits intocontainers:masterfrom
Conversation
bef0f02 to
a9007c0
Compare
a9007c0 to
b4e768b
Compare
|
Note to me: OBS currently missing Ubuntu 20.10 packages |
intentional for now, unless we get more contributors/volunteers. |
cf5e84e to
567aa39
Compare
|
Note to me: Need criu packages for Ubuntu 20.10 |
I never packaged criu for OBS. I think it would be in ubuntu repos by default, no? |
|
It might be for 20.10, previously it came from a Launchpad repo. |
567aa39 to
8948976
Compare
|
@lsm5 confirmed, |
8948976 to
6cf1395
Compare
4795caf to
cc398d3
Compare
83d0e33 to
ce03363
Compare
ce03363 to
e437459
Compare
a1ee3a9 to
d6f6744
Compare
|
|
|
Note: These images are passing tests in podman now. Giving this a positive github review will cause this PR to automatically merge. |
edsantiago
left a comment
There was a problem hiding this comment.
Some suggestions for making this a little easier to understand and maintain
Signed-off-by: Chris Evich <[email protected]>
d6f6744 to
2d594a6
Compare
Signed-off-by: Chris Evich <[email protected]>
2d594a6 to
384be09
Compare
|
Note: Marking as a draft to block automatic merging. I'd like to confirm (at least in a test PR) that the new changes don't break podman testing. |
| podman build -t $*_podman:$(call err_if_empty,IMG_SFX) \ | ||
| --build-arg=BASE_NAME=$(subst prior-,,$*) \ | ||
| --build-arg=BASE_TAG=$(call err_if_empty,BASE_TAG) \ | ||
| --build-arg=PACKER_BUILD_NAME=$(subst _podman,,$*) \ |
There was a problem hiding this comment.
Re: Scripts using conditionals based on presence/absence of 'prior' appearing in the VM/Container image name.
Can you get it from $VM_IMAGE_NAME?
That var. doesn't exist here (completely different Cirrus-CI setup). In any case, it's value is derived from $PACKER_BUILD_NAME when producing VM images. The problem area is with the container build workflow, as it shares the same setup/packaging scripts as the VM setup but does not use the packer tool.
Ordinarily the scripts could ignore this, as all conditions on $PACKER_BUILD_NAME only applied to VM's (i.e. containers don't care about setting kernel options)...except now this isn't the case, since I've un-commented the (previously commented in this PR) $ENABLE_UPDATES_TESTING conditional (on 'prior' flavors) for fedora.
I don't like this fix, it's convoluted and non-obvious 😲 (esp. in the container image build case). However, right now I cannot think of a better way to solve this in a more uniform yet readable manner, and am loathe to add a giant comment to the Makefile (which s already very dense and complex) 😞
@edsantiago I'd really like to get this PR merged, since the previously built images were already rolled out all across container-org. CI-land. Is this something we should just live with, fix later, ignore, or maybe I could file an issue on it (here) for fixing next year?
There was a problem hiding this comment.
Ooof...and it doesn't appear to work: F32 container build log sigh
There was a problem hiding this comment.
@edsantiago nvm my question, this is broken anyway so I'll clean it up and comment the heck out of it.
edsantiago
left a comment
There was a problem hiding this comment.
I thought it would be easy. Do what you need to do; revert back to the hardcoded 20-etc, that's fine.
384be09 to
b3fd469
Compare
Signed-off-by: Chris Evich <[email protected]>
This is intended to save time/resources since if container image building fails, chances are good VM images will also fail. Signed-off-by: Chris Evich <[email protected]>
b3fd469 to
58e093d
Compare
Except now that I'm aware of the problem and wrote a good comment...it would keep me up a night worrying someone might uncomment/un-hard-code this later and not realize the implications 😞 I need to re-roll and re-test the images here for the other fixes anyway, so, it's just one more thing (and I confirmed by local testing that the |
It's been completely removed from all upstream podman testing. Any failures with new images now and going forward, may be considered podman bugs. Signed-off-by: Chris Evich <[email protected]>
58e093d to
23c9930
Compare
|
|
As an alternative to #31, support multiple Ubuntu
v20.Xversions. This change will require ALL automation, in ALL repositories using these Ubuntu images to mirror the definition change:Also, ANY/ALL relevant references to
$OS_RELEASE_VERvalues must be updated, for example19->1910,20->2004or2010.