-
Notifications
You must be signed in to change notification settings - Fork 17
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
VMs: bump to f41 #392
VMs: bump to f41 #392
Conversation
Signed-off-by: Ed Santiago <santiago@redhat.com>
Something has changed in Fedora images on AWS. The us-east-1 suffix no longer exists. Remove it. Signed-off-by: Ed Santiago <santiago@redhat.com>
Lots of things seem to have changed in dnf-land. These are the changes that get us working again. Signed-off-by: Ed Santiago <santiago@redhat.com>
Changes necessary to get working VM images. I can't remember why all of these are necessary. I think the docker-compose change is because that package started bringing in too many unwanted dependencies that conflict with podman. Anyhow, this works. Signed-off-by: Ed Santiago <santiago@redhat.com>
Signed-off-by: Ed Santiago <santiago@redhat.com>
Cirrus CI build successful. Found built image names and IDs:
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
changes LGTM
if [[ "$PACKER_BUILD_NAME" == "fedora" ]] && [[ ! "$PACKER_BUILD_NAME" =~ "prior" ]]; then | ||
warn "Enabling updates-testing repository for $PACKER_BUILD_NAME" | ||
lilto ooe.sh $SUDO dnf install -y 'dnf-command(config-manager)' | ||
lilto ooe.sh $SUDO dnf config-manager --set-enabled updates-testing | ||
lilto ooe.sh $SUDO dnf config-manager setopt updates-testing.enabled=1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh I think this is why we are having older kernels in f40, the prior images are not using the updates-testing repo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you recommend?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know the history behind why we have such difference there, I have not chased the git history to end but it is there for many years so maybe better not touch that? I mean we have a workaround in podman for the kernel problem
Images built in containers/automation_images#392 Signed-off-by: Ed Santiago <santiago@redhat.com>
Images built in containers/automation_images#392 Signed-off-by: Ed Santiago <santiago@redhat.com>
Now passing in buildah thanks to Paul. I'd like to get this merged, so we can go through this again next week and see if we pick up new kernel and new pasta. |
yes agree |
Cleaned-up version of #390 because that was a mess of iterative try-this-and-that