Openwrt 25.12 version is not latest

,
1

Hi,

I noticed that the latest version of openWRT (25.12) released here is an RC5 build,not the latest stable version. In fact, they’ve been on the stable release for two weeks now. Release v25.12.0 · openwrt/openwrt · GitHub
Is there any way I can select the latest version on the Truenas container, or do I just have to wait?

image

2

Hi, there’s already an open issue about it: OpenWRT 25.12.0 builds as 25.12.0-rc5 · Issue #960 · lxc/lxc-ci · GitHub

1 Like
3

Wow, I’m glad this issue was discovered a week ago, but why hasn’t it been fixed yet?

4

Well things don’t magically happen, packaging is hard and most of the packaging work is done on people’s free time. You’re not a client here, you’re benefiting from people’s generous contributions…

5

you’re right. there is an old saying…
“nothings impossible for those that don’t do the work”

6

I must admit I feel a bit ashamed.:smiling_face_with_tear: I can compile OpenWRT on my local machine, but when it comes to Jenkins, I really don’t know how to help. If it weren’t for TrueNAS using LXC, I wouldn’t even know what LXC or J

7

Incus uses distrobuilder (GitHub - lxc/distrobuilder: System container image builder for LXC and Incus · GitHub) to generate the container images and virtual machine images. There is generic support in there for various Linux distributions. Then, you would need distrobuilder configuration files to generate each actual distribution.

Here are those configuration files, lxc-ci/images at main · lxc/lxc-ci · GitHub
Note there is an openwrt.yaml in there.

When you run distrobuilder with parameter the openwrt.yaml configuration file, you need a few extra parameters to make it work properly. You find those in the build logs at https://images.linuxcontainers.org/ It’s under the column Build Date.

If you wanted to create your own image by yourself, you would

  1. Install distrobuilder
  2. Get the openwrt.yaml configuration file (or any other if you are targeting another distro).
  3. Use the appropriate command line with distrobuilder with the proper parameters to generate the image.

If not much have changed between versions of the Linux distribution, you can easily generate images for newer or even older version. It’s that easy.

If you notice at https://images.linuxcontainers.org/, there is no VM image for OpenWRT yet. However, in the commit logs for distrobuilder and lxc-ci (links are above), there is work to generate virtual machine images for OpenWRT. Therefore, this would be a nice addition that would be appearing soon.

I also see there is no VM image yet for Kali. That would be very useful considering Kali. There is a configuration file for the container image of Kali. Kali is based on Debian, therefore, one would need to follow the Debian configuration file for a VM image, and apply to the Kali configuration file.

1 Like
8

Thank you very much for your patient explanation. I’m still a bit confused about this. If I want to upload my own image to https://images.linuxcontainers.org/ for others to use, including truenas, all I need to do is download openwrt.yaml, make the necessary changes, and then run the command, right?

distrobuilder build-dir openwrt.yaml /path/to/rootfs
distrobuilder pack-lxc openwrt.yaml /path/to/rootfs /path/to/output
distrobuilder pack-incus openwrt.yaml /path/to/rootfs /path/to/output

but, how i change openwrt version to latest in yaml

change this?

 releases:
  - snapshot
  - 23.05
  - 24.10
  - 25.12 # change to 25.12.1?
9

It’s the part I talk about the extra parameters to distrobuilder. You would need to look for build.log file which shows how to use the command line to generate the specific version.

Here’s the snippet.

distrobuilder --cache-dir /root/build/cache/ --timeout 7200 build-dir image.yaml rootfs -o image.serial=20260317_11:57 -o image.architecture=aarch64 -o image.release=25.12 -o packages.manager=apk

That’s how you generate manually an image with distrobuilder, and then you are able to properly test. That is, the version is given as a parameter.

When you run distrobuilder against a configuration file, and you specify in the command line a version like 25.12.1, distrobuilder expects to find that version number also listed in the configuration file.

1 Like