EOL the already deprecated Fedora 36 image.

GHCR isn't trusted by default.

DL3026 error: Use only an allowed registry in the FROM image

https://github.com/hadolint/hadolint/wiki/DL3026

Update: It seems to report fedora:<version> which comes from the default registry.

Fedora 37 is scheduled for end of October (ETA see schedule).

https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html

Building qtwebengine may require additional packages:

• glibc-devel.i686
• libatomic.i686
• libstdc++-static.i686

See https://pythonspeed.com/articles/security-updates-in-docker/

Using multiline label (#19) seem broken.

Periodical update the container as packages get updates independent of commits.

While the package path is working, it contains the user part twice.

Add a Fedora 36 image.

ETA: 10.05.2022

https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html

Python 3.7 has reached EOL recently.

Drop x86 support on FC >= 38 images.

Add a Trivy step as part of the CI build.

• https://github.com/aquasecurity/trivy
• https://github.com/aquasecurity/trivy-action

There's no latest tag update once #10 is merged.

Since it's used downstream, it should reflect the latest version available (fc34 for now).

Since the removal of some older files, only the base image is different.

Using Fedora 35 in yocto-build fails as repo tools cannot resolve the manifest URL as follows:

$ ./dev/bootstrap.sh 
Trying to pull ghcr.io/jhnc-oss/yocto-image/yocto:35...
Getting image source signatures
Copying blob c3f6bed8a317 skipped: already exists  
Copying blob bd072b7c7ca5 skipped: already exists  
Copying blob 5e2b998ecd07 [--------------------------------------] 0.0b / 0.0b
Copying blob 9ada86c2f90d [--------------------------------------] 0.0b / 0.0b
Copying config 1043c59718 done  
Writing manifest to image destination
Storing signatures
+ set -o errexit
+ MANIFEST_BRANCH=main
+ MANIFEST_URL=https://github.com/jhnc-oss/yocto-manifests.git
+ repo init --manifest-url https://github.com/jhnc-oss/yocto-manifests.git --no-clone-bundle --depth=1 --manifest-branch main
Downloading manifest from https://github.com/jhnc-oss/yocto-manifests.git
fatal: unable to access 'https://github.com/jhnc-oss/yocto-manifests.git/': getaddrinfo() thread failed to start
manifests: sleeping 4.0 seconds before retrying
fatal: unable to access 'https://github.com/jhnc-oss/yocto-manifests.git/': getaddrinfo() thread failed to start
fatal: cannot obtain manifest https://github.com/jhnc-oss/yocto-manifests.git

Basic CI build to ensure a buildable state.

The UID used currently conflicts, 2000 should be used instead.

The readme examples are outdated.

The localedef call can break locales and prevent containers from starting. Even though the execution succeeds, it errors actually (shown with verbose output enabled).

Locales are set correctly without localdef, therefore it shouldn't be necessary anyway.

Issues reported by Hadolint don't cause a build failure. Issues are reported in the build overview though.

Fedora 39 has been released.

Add a Dockerfile linting as part of the CI build.

FC32 and 33 are EOL and no longer part of the build.

Fedora 35 has reached EOL last year (https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html).

Fedora 38 will be released soon: https://fedorapeople.org/groups/schedule/f-38/f-38-key-tasks.html

Add and deploy a Fedora 32 image. FC34 isn't fully compatible yet.

Fedora 33 becomes EOL on Tue 2021-11-30.

Stale untagged images aren't removed.

Add a Fedora 40 based image.

ETA: 2024-04-16 / 2024-04-23

https://fedorapeople.org/groups/schedule/f-40/f-40-key-tasks.html

Shall we drop the latest tag? In my opinion it doesn't make much sense to use in the Yocto scenario.

Deploy the Image to the ghcr.

Avoid warnings regarding Git default branches by setting it explicitly.

Install and configure repo.

The Fedora 35 build fails due to package conflict:

 Error: Transaction test error:
  file /usr/share/vim/vim82/defaults.vim from install of vim-common-2:8.2.3642-1.fc35.x86_64 conflicts with file from package vim-minimal-2:8.2.3568-1.fc35.x86_64

This issue is likely caused upstream, since the unchanged commit was green previously.

Fedora 35 is announced for next week.

ETA 26.10.2021 Early November 2021