docker-ce-packaging icon indicating copy to clipboard operation
docker-ce-packaging copied to clipboard

[master] fix and refactor static packages with fixed cross-comp on moby

Open crazy-max opened this issue 3 years ago • 1 comments

follow-up https://github.com/docker/docker-ce-packaging/pull/665#issuecomment-1173088399

this builds the docker engine from https://github.com/moby/moby/pull/43529 which fixes issues with cross compilation to remove unneeded logic.

it also fixes cross comp for extra tools (containerd, runc, tini, etc...) which is currently not cover on master branch but fixed in https://github.com/moby/moby/pull/43529.

see last commit

crazy-max avatar Jul 06 '22 12:07 crazy-max

https://ci-next.docker.com/public/blue/organizations/jenkins/docker-ce-packaging/detail/PR-718/10/pipeline/1259#step-1369-log-373

#63 [linux/arm/v6 all 1/1] COPY --link --from=release-all /out /
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xa0ba90]

goroutine 26 [running]:
github.com/moby/buildkit/util/progress/progressui.(*textMux).print(0x4000687df8, 0x4000687e70)
	/go/src/github.com/docker/buildx/vendor/github.com/moby/buildkit/util/progress/progressui/printer.go:284 +0x590
github.com/moby/buildkit/util/progress/progressui.DisplaySolveStatus(0x1db83a0, 0x400023c140, 0x0, 0x0, 0x0, 0x0, 0x1d727a0, 0x4000010020, 0x4000134480, 0x0, ...)
	/go/src/github.com/docker/buildx/vendor/github.com/moby/buildkit/util/progress/progressui/display.go:83 +0x2b0
github.com/docker/buildx/util/progress.NewPrinter.func1(0x1a9fe45, 0x4, 0x400039e410, 0x1dc1f18, 0x4000010020, 0x1db83a0, 0x400023c140, 0x4000134480, 0x40005ec4b0, 0x40001344e0)
	/go/src/github.com/docker/buildx/util/progress/printer.go:99 +0xdc
created by github.com/docker/buildx/util/progress.NewPrinter
	/go/src/github.com/docker/buildx/util/progress/printer.go:87 +0x18c
make[1]: *** [Makefile:44: build] Error 2

looks like the jenkins nodes are using buildx 0.8.1, this should be fixed with buildx 0.8.2.

@thaJeztah can you update buildx on the nodes?

crazy-max avatar Jul 20 '22 08:07 crazy-max