Skip to content

Upgrade to Fedora 45 and Go 1.27 - #165

Merged
alicefr merged 7 commits into
bootc-dev:mainfrom
HarshwardhanPatil07:fedora45-go127
Nov 16, 2026
Merged

alicefr merged 7 commits into
bootc-dev:mainfrom
HarshwardhanPatil07:fedora45-go127

Conversation

@HarshwardhanPatil07

Copy link
Copy Markdown
Member

closes: #164

@HarshwardhanPatil07
HarshwardhanPatil07 force-pushed the fedora45-go127 branch 2 times, most recently from 833900f to 472dce2 Compare November 13, 2026 09:30
Build the CLI container on Fedora 45 and set the module to Go 1.27. Pin the Ginkgo command through the Go tool declaration so the build uses the module version.

Assisted-by: AI
Signed-off-by: HarshwardhanPatil07 <harshpat@redhat.com>
Build bootc nodes, disk images, and helper images from Fedora 45. Have integration CI produce and test the Fedora 45 node tags before the CLI default is changed.

Assisted-by: AI
Signed-off-by: HarshwardhanPatil07 <harshpat@redhat.com>
Refresh direct and indirect modules for the Fedora 45 and Go 1.27 build while keeping the Kubernetes dependency set compatible.

Assisted-by: AI
Signed-off-by: HarshwardhanPatil07 <harshpat@redhat.com>
Go 1.27 vet rejects wrapping the pointer error model directly with percent-w. Join it with context so errors.Is still sees the intended error.

Assisted-by: AI
Signed-off-by: HarshwardhanPatil07 <harshpat@redhat.com>
The node image build failed when the runner AppArmor profile denied bwrap the dac_override capability. Use one checked runner setup after package installation in every affected job, so the build and runtime tests get the same policy state.

Assisted-by: AI
Signed-off-by: HarshwardhanPatil07 <harshpat@redhat.com>
Fedora 45 installs the default image signature policy under /usr/share/containers, while CRI-O 1.36 still searches /etc/containers. Install the policy provider explicitly and point CRI-O to the packaged policy so control-plane pods can start.

The nested container test cached a Kubernetes 1.35 node image even though bink defaults to 1.36. Cache the image actually used so nested Podman does not need to pull it through its unreliable DNS path.

Assisted-by: AI
Signed-off-by: HarshwardhanPatil07 <harshpat@redhat.com>
The nested test forced 8.8.8.8 as its resolver. In PR 165 CI, lookups through that resolver failed for Kubernetes and Calico images, leaving the cluster image volume incomplete and CoreDNS unready. Let Podman provide the outer container resolver, which the host-network populator can use.

Assisted-by: AI
Signed-off-by: HarshwardhanPatil07 <harshpat@redhat.com>
@HarshwardhanPatil07

Copy link
Copy Markdown
Member Author

@alicefr this ones ready

# The outer container's resolv.conf points to the host's aardvark-dns, which is
# unreachable from inside nested podman networks. Override it so inner aardvark-dns
# forwards queries to a public resolver instead.
podman exec "${nested_container}" bash -c 'echo "nameserver 8.8.8.8" > /etc/resolv.conf'

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

@alicefr alicefr left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Many many thanks for doing the upgrade! LGTM

@alicefr
alicefr merged commit 851e8db into bootc-dev:main Nov 16, 2026
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Upgrade bink to Fedora 45 and Go 1.27

2 participants