chore: upgrade github.com/docker/cli to v29 #1547

Merged

mfenniak merged 1 commit from aahlenst/runner:docker-29 into main 2026-07-19 14:58:12 +00:00

Conversation 12 Commits 1 Files changed 28 +1196 -847

aahlenst commented 2026-06-02 18:04:35 +00:00

Member

• Copy link
• Copy Markdown

Update the Docker client libraries from v28 to v29 because v28 is no longer maintained. The minimum requirement for Docker has been raised to Docker 25.0.

Users of Debian 13 (Trixie) or 12 (Bookworm) that use IPv6 are affected by a bug in the Docker version shipped by Debian that results in error messages like:

2026/07/01 14:58:59 Could not get list of networks: ParseAddr("fd05:d0ca:2::1/112"): unexpected character, want colon (at "/112")

Affected Debian users should either not upgrade Forgejo Runner or switch to the Docker package provided by Docker until the problem is either resolved by the Docker or Debian developers.

• other
  • PR: chore: upgrade github.com/docker/cli to v29

Update the Docker client libraries from v28 to v29 because v28 is no longer maintained. The minimum requirement for Docker has been raised to Docker 25.0. Users of Debian 13 (Trixie) or 12 (Bookworm) that use IPv6 [are affected by a bug](https://github.com/moby/moby/pull/49520) in the Docker version shipped by Debian that results in error messages like: ``` 2026/07/01 14:58:59 Could not get list of networks: ParseAddr("fd05:d0ca:2::1/112"): unexpected character, want colon (at "/112") ``` Affected Debian users should either not upgrade Forgejo Runner or switch to the Docker package provided by Docker until the problem is either resolved by the Docker or Debian developers. <!--start release-notes-assistant--> <!--URL:https://code.forgejo.org/forgejo/runner--> - other - [PR](https://code.forgejo.org/forgejo/runner/pulls/1547): <!--number 1547 --><!--line 0 --><!--description Y2hvcmU6IHVwZ3JhZGUgZ2l0aHViLmNvbS9kb2NrZXIvY2xpIHRvIHYyOQ==-->chore: upgrade github.com/docker/cli to v29<!--description--> <!--end release-notes-assistant-->

aahlenst force-pushed docker-29 from 63ff6aeb18 to 9f5a5046a6 2026-06-02 19:15:40 +00:00 Compare

aahlenst force-pushed docker-29 from 9f5a5046a6 to a4c12f58ec 2026-06-02 19:23:24 +00:00 Compare

aahlenst commented 2026-06-02 20:12:08 +00:00

Author

Member

• Copy link
• Copy Markdown

It looks like this update hits https://github.com/moby/moby/pull/49520 with the Docker version included in Debian 13. That's why the forgejo-runner exec job fails.

In short, Docker includes the network prefix in the gateway's address when creating IPv6 networks. This causes netip.ParseAddr() inside the Docker API to fail when fetching the list of networks. There isn't really a way around fetching the list of networks because we only have the network's name and need it's ID to operate on it.

Do we accept that and recommend that users that need IPv6 upgrade to the Docker version shipped by Docker?

It looks like this update hits https://github.com/moby/moby/pull/49520 with the Docker version included in Debian 13. That's why the `forgejo-runner exec` job fails. In short, Docker includes the network prefix in the gateway's address when creating IPv6 networks. This causes `netip.ParseAddr()` inside the Docker API to fail when fetching the list of networks. There isn't really a way around fetching the list of networks because we only have the network's name and need it's ID to operate on it. Do we accept that and recommend that users that need IPv6 upgrade to the Docker version shipped by Docker?

mfenniak commented 2026-06-06 01:22:19 +00:00

Owner

• Copy link
• Copy Markdown

@aahlenst wrote in #1547 (comment):

Do we accept that and recommend that users that need IPv6 upgrade to the Docker version shipped by Docker?

Hm... the docker-stable test runs on Debian Bookworm. Debian's primary support EOL for Bookworm is 10 June 2026... huh... that's rather soon... but then it transitions to long-term support until 2028. It's fairly reasonable to assume people will be running it for a while.

I understand this dependency upgrade isn't being done because of specific value added, but as an inevitable requirement. Eventually we'll want to use an API that requires an updated client, or be affected by a bug or security issue.

I think it seems reasonable to move forward with this change. Doesn't seem right for us to be stuck on a dependency because of a slow-moving distro with long-term support, especially when there's a pathway for such users to address it: update their Docker dependency independent of their OS.

I'm thinking we should consider it a breaking change, and document the minimum Docker version required for compatibility. And then... probably do a v13? We could tackle the other v13 issues that we've discussed in the same time. (We could either hold this PR and others unmerged, or, do a temporary v13 branch -- but keep main releasable for a few weeks while we get those v13 issues ready.)

@aahlenst wrote in https://code.forgejo.org/forgejo/runner/pulls/1547#issuecomment-89368: > Do we accept that and recommend that users that need IPv6 upgrade to the Docker version shipped by Docker? Hm... the docker-stable test runs on Debian Bookworm. Debian's primary support EOL for Bookworm is 10 June 2026... huh... that's rather soon... but then it transitions to [long-term support](https://wiki.debian.org/LTS) until 2028. It's fairly reasonable to assume people will be running it for a while. I understand this dependency upgrade isn't being done because of specific value added, but as an inevitable requirement. Eventually we'll want to use an API that requires an updated client, or be affected by a bug or security issue. I think it seems reasonable to move forward with this change. Doesn't seem right for us to be stuck on a dependency because of a slow-moving distro with long-term support, especially when there's a pathway for such users to address it: update their Docker dependency independent of their OS. I'm thinking we should consider it a breaking change, and document the minimum Docker version required for compatibility. And then... probably do a v13? We could tackle the other v13 issues that we've discussed in the same time. (We could either hold this PR and others unmerged, or, do a temporary v13 branch -- but keep `main` releasable for a few weeks while we get those v13 issues ready.)

aahlenst commented 2026-06-06 10:56:37 +00:00

Author

Member

• Copy link
• Copy Markdown

@mfenniak wrote in #1547 (comment):

Hm... the docker-stable test runs on Debian Bookworm. Debian's primary support EOL for Bookworm is 10 June 2026... huh... that's rather soon... but then it transitions to long-term support until 2028. It's fairly reasonable to assume people will be running it for a while.

Unfortunately, the impact is much bigger. My test machine uses Debian 13. That's Trixie. And it has the same problem. It affects Docker versions < 27. Interestingly, Canonical has added Docker 29 to Ubuntu 24.04.

Forgejo Runner is not the only software that seems to be affected.

I understand this dependency upgrade isn't being done because of specific value added, but as an inevitable requirement. Eventually we'll want to use an API that requires an updated client, or be affected by a bug or security issue.

Correct.

I'm thinking we should consider it a breaking change, and document the minimum Docker version required for compatibility. And then... probably do a v13?

Technically, the minimal version is 25.0. It's only a problem if you run into that Docker bug with IPv6. Doing a major version because of that seems kinda... extreme?

Lobbying the Moby folks to make their parsing more lenient would be a possibility, too.

If we decide to do v13, my preference would be a temporary branch. Fewer merge conflicts, easier to test, ...

@mfenniak wrote in https://code.forgejo.org/forgejo/runner/pulls/1547#issuecomment-90706: > Hm... the docker-stable test runs on Debian Bookworm. Debian's primary support EOL for Bookworm is 10 June 2026... huh... that's rather soon... but then it transitions to [long-term support](https://wiki.debian.org/LTS) until 2028. It's fairly reasonable to assume people will be running it for a while. Unfortunately, the impact is much bigger. My test machine uses Debian 13. That's Trixie. And it has the same problem. It affects Docker versions < 27. Interestingly, Canonical has added Docker 29 to Ubuntu 24.04. Forgejo Runner is not the only software that seems to be affected. > I understand this dependency upgrade isn't being done because of specific value added, but as an inevitable requirement. Eventually we'll want to use an API that requires an updated client, or be affected by a bug or security issue. Correct. > I'm thinking we should consider it a breaking change, and document the minimum Docker version required for compatibility. And then... probably do a v13? Technically, the [minimal version is 25.0](https://github.com/moby/moby/releases/tag/docker-v29.0.0). It's only a problem if you run into that Docker bug with IPv6. Doing a major version because of that seems kinda... extreme? Lobbying the Moby folks to make their parsing more lenient would be a possibility, too. If we decide to do v13, my preference would be a temporary branch. Fewer merge conflicts, easier to test, ...

mfenniak commented 2026-06-06 13:57:57 +00:00

Owner

• Copy link
• Copy Markdown

@aahlenst wrote in #1547 (comment):

Technically, the minimal version is 25.0. It's only a problem if you run into that Docker bug with IPv6. Doing a major version because of that seems kinda... extreme?

Link is to v29, text says v25?

My thought process on a major version is kinda simple: we did v12.0.0 when we added git as an external dependency, and the release of this PR would bump the minimum supported version of an external dependency.

I guess it could be argued that the combination of having an IPv6 network on your Docker system, and using a >6 month old Docker release, may not be a common combination. But we do know there are users with the IPv6 facet at least (#1399, #119). And I'm not sure if common matters, as we're planning other v13 things that also won't affect common users (eg. removing DOCKER_PASSWORD). The major version bump just waves a small flag to people saying, "pay attention on this upgrade".

@aahlenst wrote in https://code.forgejo.org/forgejo/runner/pulls/1547#issuecomment-90728: > Technically, the [minimal version is 25.0](https://github.com/moby/moby/releases/tag/docker-v29.0.0). It's only a problem if you run into that Docker bug with IPv6. Doing a major version because of that seems kinda... extreme? Link is to v29, text says v25? My thought process on a major version is kinda simple: we did v12.0.0 when we added `git` as an external dependency, and the release of this PR would bump the minimum supported version of an external dependency. I guess it could be argued that the combination of having an IPv6 network on your Docker system, and using a >6 month old Docker release, may not be a common combination. But we do know there are users with the IPv6 facet at least (#1399, #119). And I'm not sure if common matters, as we're planning other v13 things that also won't affect common users (eg. removing `DOCKER_PASSWORD`). The major version bump just waves a small flag to people saying, "pay attention on this upgrade".

aahlenst commented 2026-06-06 14:14:21 +00:00

Author

Member

• Copy link
• Copy Markdown

@mfenniak wrote in #1547 (comment):

Link is to v29, text says v25?

Yes, because we would update to v29 and the oldest supported version of v29 is documented in there.

The major version bump just waves a small flag to people saying, "pay attention on this upgrade".

I'm not opposed. Waiting forever makes upgrading more painful.

@mfenniak wrote in https://code.forgejo.org/forgejo/runner/pulls/1547#issuecomment-90735: > Link is to v29, text says v25? Yes, because we would update to v29 and the oldest supported version of v29 is documented in there. > The major version bump just waves a small flag to people saying, "pay attention on this upgrade". I'm not opposed. Waiting forever makes upgrading more painful.

viceice referenced this pull request 2026-07-07 10:52:16 +00:00

Update module github.com/docker/cli to v29 [SECURITY] #1584

viceice referenced this pull request 2026-07-07 10:52:32 +00:00

Update module github.com/docker/go-connections to v0.7.0 #1562

aahlenst commented 2026-07-13 18:05:28 +00:00

Author

Member

• Copy link
• Copy Markdown

A while ago I raised an issue upstream about the Debian-related problems: https://github.com/moby/moby/issues/52991. It looks like the Debian maintainers are going to fix Docker in Trixie. Otherwise, the Docker people might do something about it.

A while ago I raised an issue upstream about the Debian-related problems: https://github.com/moby/moby/issues/52991. It looks like the Debian maintainers are going to fix Docker in Trixie. Otherwise, the Docker people might do something about it.

Gusted commented 2026-07-14 23:31:08 +00:00

Owner

• Copy link
• Copy Markdown

@mfenniak wrote in #1547 (comment):

distro with long-term support

I have a double edge sword with such support schemes, users (or I rather assume companies) want to stay stable on a OS and presumably receive as little (security) fixes possible to stay bug-compatible. Then why would they continuously upgrade Forgejo runner to the latest version? AFAIK you could simply stop upgrading and you can still connect to a Forgejo v16 instance.

@mfenniak wrote in https://code.forgejo.org/forgejo/runner/pulls/1547#issuecomment-90706: > distro with long-term support I have a double edge sword with such support schemes, users (or I rather assume companies) want to stay stable on a OS and presumably receive as little (security) fixes possible to stay bug-compatible. Then why would they continuously upgrade Forgejo runner to the latest version? AFAIK you could simply stop upgrading and you can still connect to a Forgejo v16 instance.

👍 1

aahlenst force-pushed docker-29 from a4c12f58ec to 2fa2ba88ef 2026-07-15 14:39:47 +00:00 Compare

aahlenst commented 2026-07-15 15:07:11 +00:00

Author

Member

• Copy link
• Copy Markdown

I've updated the PR and altered the problematic CI workflow. Like integration-tests-with-docker, it's now a matrix job that runs with the Docker version included in Debian and the one distributed by Docker. I've commented out the Docker version included in Debian because that's going to fail until https://github.com/moby/moby/issues/52991 is resolved. I've added a comment that indicates that.

I've updated the PR and altered the problematic CI workflow. Like `integration-tests-with-docker`, it's now a matrix job that runs with the Docker version included in Debian and the one distributed by Docker. I've commented out the Docker version included in Debian because that's going to fail until https://github.com/moby/moby/issues/52991 is resolved. I've added a comment that indicates that.

🎉 1

viceice commented 2026-07-15 15:47:34 +00:00

Owner

• Copy link
• Copy Markdown

can we run on Trixie? it should have a newer docker version

can we run on Trixie? it should have a newer docker version

aahlenst commented 2026-07-15 17:48:26 +00:00

Author

Member

• Copy link
• Copy Markdown

@viceice wrote in #1547 (comment):

can we run on Trixie? it should have a newer docker version

Yes, but it doesn't help, because Docker on Trixie is too old, too. The backport in question would be for Trixie. Bookworm's full support has ended last month. Switching to Trixie would make sense anyway.

@viceice wrote in https://code.forgejo.org/forgejo/runner/pulls/1547#issuecomment-94819: > can we run on Trixie? it should have a newer docker version Yes, but it doesn't help, because Docker on Trixie is too old, too. The backport in question would be for Trixie. Bookworm's full support has ended last month. Switching to Trixie would make sense anyway.

aahlenst force-pushed docker-29 from 2fa2ba88ef to 248fc1d300 2026-07-15 17:53:10 +00:00 Compare

aahlenst added the

Kind/Breaking

Kind/Chore

run-end-to-end-tests

labels 2026-07-15 17:59:43 +00:00

cascading-pr referenced this pull request from actions/setup-forgejo 2026-07-15 19:12:31 +00:00

cascading-pr from https://code.forgejo.org/forgejo/runner refs/pull/1547/head to forgejo/runner-1547 #1044

cascading-pr commented 2026-07-15 19:12:32 +00:00

Contributor

• Copy link
• Copy Markdown

cascading-pr updated at actions/setup-forgejo#1044

cascading-pr updated at https://code.forgejo.org/actions/setup-forgejo/pulls/1044

aahlenst force-pushed docker-29 from 248fc1d300 to 0d57c2e9cd 2026-07-18 10:56:07 +00:00 Compare

cascading-pr commented 2026-07-18 10:56:16 +00:00

Contributor

• Copy link
• Copy Markdown

cascading-pr updated at actions/setup-forgejo#1044

cascading-pr updated at https://code.forgejo.org/actions/setup-forgejo/pulls/1044

mfenniak merged commit 9ffa185850 into main 2026-07-19 14:58:12 +00:00

mfenniak referenced this pull request from a commit 2026-07-19 14:58:14 +00:00

chore: upgrade github.com/docker/cli to v29 (#1547)

viceice-bot referenced this pull request 2026-08-24 20:45:37 +00:00

Update forgejo-runner to v13 #1706

mfenniak referenced this pull request from a commit 2026-08-24 21:22:44 +00:00

Update forgejo-runner to v13 (#1706)

viceice-bot referenced this pull request from actions/setup-forgejo 2026-09-01 00:21:18 +00:00

Update dependency forgejo/runner to v13 #1107

mfenniak referenced this pull request from a commit 2026-09-01 01:51:26 +00:00

Update dependency forgejo/runner to v13 (#1107)

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

FreeBSD

  

Kind/Breaking

Breaking change that won't be backward compatible

  

Kind/Bug

Something is not working

  

Kind/Chore

It is no fun but it needs to be done, this is a chore.

  

Kind/DependencyUpdate

for pull requests that are created by renovate when updating a dependency

  

Kind/Documentation

Documentation changes

  

Kind/Enhancement

Improve existing functionality

  

Kind/Feature

New functionality

  

Kind/Security

This is security issue

  

Kind/Testing

Issue or pull request related to testing

  

Priority

Critical

The priority is critical

  

Priority

High

The priority is high

  

Priority

Low

The priority is low

  

Priority

Medium

The priority is medium

  

Reviewed

Confirmed

Issue has been confirmed

  

Reviewed

Duplicate

This issue or pull request already exists

  

Reviewed

Invalid

Invalid issue

  

Reviewed

Won't Fix

This issue won't be fixed

  

Status

Abandoned

Somebody has started to work on this but abandoned work

  

Status

Blocked

Something is blocking this issue or pull request

  

Status

Need More Info

Feedback is required to reproduce issue or to continue work

  

Windows

Windows ports is an independent project, see https://github.com/Crown0815/Forgejo-runner-windows-builder

  

linux-powerpc64le

powerpc64le

  

linux-riscv64

  

linux-s390x

  

run-end-to-end-tests

Run https://code.forgejo.org/forgejo/end-to-end with a runner compiled from this pull request

  

run-forgejo-tests

Run https://codeberg.org/forgejo/forgejo tests importing the runner from this pull request

  

run-multi-platform-tests

Label a PR for automatic execution of test suite on arm64 architecture.

No labels

FreeBSD

Kind/Breaking

Kind/Bug

Kind/Chore

Kind/DependencyUpdate

Kind/Documentation

Kind/Enhancement

Kind/Feature

Kind/Security

Kind/Testing

Priority

Critical

Priority

High

Priority

Low

Priority

Medium

Reviewed

Confirmed

Reviewed

Duplicate

Reviewed

Invalid

Reviewed

Won't Fix

Status

Abandoned

Status

Blocked

Status

Need More Info

Windows

linux-powerpc64le

linux-riscv64

linux-s390x

run-end-to-end-tests

run-forgejo-tests

run-multi-platform-tests

Milestone

Clear milestone

No items

No milestone

Assignees

Clear assignees

No assignees

5 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

forgejo/runner!1547

No description provided.