Docker package a bit behind releases #68

New Issue

2026-10-04T22:59:17+02:00

adam commented

2026-10-04 22:59:17 +02:00

Hi @l5yth!

I've noticed the official docker releases are a bit behind the main release (e.g. 0.5.3).

I've been building packages on my own to keep up with latest, but would it be possible to automate the building/release of packages when the mainline version is updated?

Wasn't sure if that was a manual process for you; happy to help if I can.

Hi @l5yth! I've noticed the [official docker releases](https://github.com/l5yth?tab=packages&repo_name=potato-mesh) are a bit behind the main release (e.g. `0.5.3`). I've been building packages on my own to keep up with latest, but would it be possible to automate the building/release of packages when the mainline version is updated? Wasn't sure if that was a manual process for you; happy to help if I can.

adam closed this issue

2026-10-04 22:59:18 +02:00

adam commented

2026-10-04 22:59:18 +02:00

What dou mean with 'behind'? Your link shows an image tagged with 0.5.3.
Or do you mean the contents of the image? @nicjansma

Maybe my problem is related to this issue: I created a container from image ghcr.io/l5yth/potato-mesh-web-linux-amd64:latest (today). But the web app shows in footer 0.3.0. I also used the new environment variables described in https://github.com/l5yth/potato-mesh/releases/tag/v0.5.0 but at runtime the default values for some environment variables are used, with the old names.

This leads me to the assumption that inside of the latest docker image is an old version. Is this correct or is there another issue? @l5yth

What dou mean with 'behind'? Your link shows an image tagged with 0.5.3. Or do you mean the contents of the image? @nicjansma Maybe my problem is related to this issue: I created a container from image ghcr.io/l5yth/potato-mesh-web-linux-amd64:latest (today). But the web app shows in footer 0.3.0. I also used the new environment variables described in https://github.com/l5yth/potato-mesh/releases/tag/v0.5.0 but at runtime the default values for some environment variables are used, with the old names. This leads me to the assumption that inside of the latest docker image is an old version. Is this correct or is there another issue? @l5yth

adam commented

2026-10-04 22:59:19 +02:00

@BigBen500
There is something wrong on your side. :Latest wich I pulled is 0.5.3.

It would be nice if latest is realy the latest or a nightly build would be nice

@BigBen500 There is something wrong on your side. :Latest wich I pulled is 0.5.3. It would be nice if latest is realy the latest or a nightly build would be nice

adam commented

2026-10-04 22:59:20 +02:00

@Delta1977 After re-deployment of container engine it works now correctly.

@Delta1977 After re-deployment of container engine it works now correctly.

adam commented

2026-10-04 22:59:21 +02:00

@BigBen500
It would be nice if latest is realy the latest or a nightly build would be nice

Whenever I test new features or bug fixes, I tag dev releases which will be mapped to latest.

There is really not much more I need to do as I do not iterate on this every day.

> @BigBen500 > It would be nice if latest is realy the latest or a nightly build would be nice Whenever I test new features or bug fixes, I tag dev releases which will be mapped to latest. There is really not much more I need to do as I do not iterate on this every day.

adam commented

2026-10-04 22:59:21 +02:00

When I had opened this message earlier this week, potato-mesh-web-linux-amd64:latest was at 0.3.0

I've re-pulled :latest and it's showing 0.5.3.

Thanks!

When I had opened this message earlier this week, `potato-mesh-web-linux-amd64:latest` was at `0.3.0` I've re-pulled `:latest` and it's showing `0.5.3`. Thanks!

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/potato-mesh#68