Skip to content

fix(docker): use dashes instead of colons in PR build version string#640

Merged
bodji merged 1 commit intoroot-gg:masterfrom
bodji:fix/docker-build-tar-colon
Feb 25, 2026
Merged

fix(docker): use dashes instead of colons in PR build version string#640
bodji merged 1 commit intoroot-gg:masterfrom
bodji:fix/docker-build-tar-colon

Conversation

@bodji
Copy link
Copy Markdown
Member

@bodji bodji commented Feb 25, 2026

What

Replace colons with dashes in the VERSION string computed by the PR Docker build workflow.

Why

Colons in the archive filename (e.g. plik-server-1.4-RC4:pr-636:58d5275c-linux-arm.tar.gz) cause tar to interpret the filename as a remote host path (host:path), failing with "Cannot connect to plik-server-1.4-RC4: resolve failed".

Changes

  • .github/workflows/docker-build-pr.yaml: change VERSION separator from : to -

Testing

  • YAML validated
  • Verified the resulting filename plik-server-1.4-RC4-pr-636-58d5275c-linux-arm.tar.gz contains no special characters

Colons in the VERSION string caused tar to interpret the archive
filename as a remote host path (e.g. plik-server-1.4-RC4:pr-636:abc
is parsed as host:path), breaking the build with "resolve failed".
@bodji bodji merged commit ef9d0fa into root-gg:master Feb 25, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant