Skip to content

docs: update Docker deployment docs for bridge networking migration #750

docs: update Docker deployment docs for bridge networking migration

docs: update Docker deployment docs for bridge networking migration #750

Triggered via pull request March 23, 2026 07:52
Status Success
Total duration 5m 17s
Artifacts

commons-ci.yml

on: pull_request
Matrix: build-commons
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 1 warning
build-commons (11)
expected:<Fri Jan 02 15:54:17 UTC 1> but was:<Sat Jan 03 00:00:00 UTC 1>
build-commons (11)
expected:<Fri Jan 02 15:54:17 UTC 1> but was:<Sat Jan 03 00:00:00 UTC 1>
build-commons (11)
expected:<Fri Jan 02 15:54:17 UTC 1> but was:<Sat Jan 03 00:00:00 UTC 1>
build-commons (11)
expected:<Fri Jan 02 15:54:17 UTC 1> but was:<Sat Jan 03 00:00:00 UTC 1>
build-commons (11)
expected:<Fri Jan 02 15:54:17 UTC 1> but was:<Sat Jan 03 00:00:00 UTC 1>
build-commons (11)
expected:<Fri Jan 02 15:54:17 UTC 1> but was:<Sat Jan 03 00:00:00 UTC 1>
build-commons (11)
expected:<Fri Jan 02 15:54:17 UTC 1> but was:<Sat Jan 03 00:00:00 UTC 1>
build-commons (11)
expected:<Fri Jan 02 15:54:17 UTC 1> but was:<Sat Jan 03 00:00:00 UTC 1>
build-commons (11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, codecov/codecov-action@v3.0.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/