-
Notifications
You must be signed in to change notification settings - Fork 161
[master] fix build-script for docker-proxy (after libnetwork integration) and update to Go 1.16.5 #554
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[master] fix build-script for docker-proxy (after libnetwork integration) and update to Go 1.16.5 #554
Conversation
libnetwork has been integrated in the docker/docker (moby) repository, and now is compiled as part of hack/make.sh dynbinary. Signed-off-by: Sebastiaan van Stijn <[email protected]>
Signed-off-by: Sebastiaan van Stijn <[email protected]>
This comment has been minimized.
This comment has been minimized.
|
According to https://bugs.centos.org/view.php?id=18212 / ComplianceAsCode/content#7016, looks like upgrading to libarchive-3.3.3-1.el8.x86_64 should resolve the problem. |
Trying to fix
+ echo 'Install tini version de40ad007797e0dcd8b7126f27bb87401d224240'
+ git clone https://github.com/krallin/tini.git /go/tini
Install tini version de40ad007797e0dcd8b7126f27bb87401d224240
Cloning into '/go/tini'...
+ cd /go/tini
+ git checkout -q de40ad007797e0dcd8b7126f27bb87401d224240
+ cmake .
cmake: symbol lookup error: cmake: undefined symbol: archive_write_add_filter_zstd
error: Bad exit status from /var/tmp/rpm-tmp.Dl5CDf (%build)
According to https://bugs.centos.org/view.php?id=18212, upgrading to libarchive-3.3.3-1.el8.x86_64
should resolve the problem.
Signed-off-by: Sebastiaan van Stijn <[email protected]>
Not sure why, but looks like the path used `<arch>-daemon` (instead of just `<arch>`).
However, it's not consistent either, because `containerutility.exe` is in `<arch>`?
When running:
make REF=master checkout
make REF=master DOCKER_BUILD_PKGS=cross-win static
The build failed:
mkdir -p build/win/amd64/docker
cp /Users/sebastiaan/go/src/github.com/docker/docker-ce-packaging/src/github.com/docker/cli/build/docker-windows-amd64.exe build/win/amd64/docker/docker.exe
cp /Users/sebastiaan/go/src/github.com/docker/docker-ce-packaging/src/github.com/docker/docker/bundles/cross/windows/amd64/dockerd-0.0.0-20210629140245-4a6fe51.exe build/win/amd64/docker/dockerd.exe
cp: /Users/sebastiaan/go/src/github.com/docker/docker-ce-packaging/src/github.com/docker/docker/bundles/cross/windows/amd64/dockerd-0.0.0-20210629140245-4a6fe51.exe: No such file or directory
make[1]: *** [cross-win] Error 1
make: *** [static] Error 2
This is what's in bundles:
tree /Users/sebastiaan/go/src/github.com/docker/docker-ce-packaging/src/github.com/docker/docker/bundles/
/Users/sebastiaan/go/src/github.com/docker/docker-ce-packaging/src/github.com/docker/docker/bundles/
└── cross
└── windows
├── amd64
│ └── containerutility.exe
└── amd64-daemon
├── docker-proxy-0.0.0-20210629140245-4a6fe51.exe
├── docker-proxy-0.0.0-20210629140245-4a6fe51.exe.md5
├── docker-proxy-0.0.0-20210629140245-4a6fe51.exe.sha256
├── docker-proxy.exe -> docker-proxy-0.0.0-20210629140245-4a6fe51.exe
├── dockerd-0.0.0-20210629140245-4a6fe51.exe
├── dockerd-0.0.0-20210629140245-4a6fe51.exe.md5
├── dockerd-0.0.0-20210629140245-4a6fe51.exe.sha256
└── dockerd.exe -> dockerd-0.0.0-20210629140245-4a6fe51.exe
Signed-off-by: Sebastiaan van Stijn <[email protected]>
| cp $(ENGINE_DIR)/bundles/cross/windows/amd64-daemon/dockerd-$(GEN_STATIC_VER).exe build/win/amd64/docker/dockerd.exe | ||
| cp $(ENGINE_DIR)/bundles/cross/windows/amd64-daemon/docker-proxy-$(GEN_STATIC_VER).exe build/win/amd64/docker/dockerd.exe |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR fixes the issue, but after this I want to look in the upstream moby repository "why" this path changed, because there's also some inconsistency here (<arch>-daemon for some binaries, and <arch> for others); see 09541b5
fredericdalleau
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
libnetwork has been integrated in the docker/docker (moby) repository, and now is compiled as part of hack/make.sh dynbinary.
relates to moby/moby#42262 and moby/moby#42539