Skip to content

[test] update to runc v1.2.0-rc.2#5157

Closed
tonistiigi wants to merge 1 commit intomoby:masterfrom
tonistiigi:runc-v1.2.0-rc.2
Closed

[test] update to runc v1.2.0-rc.2#5157
tonistiigi wants to merge 1 commit intomoby:masterfrom
tonistiigi:runc-v1.2.0-rc.2

Conversation

@tonistiigi
Copy link
Copy Markdown
Member

No description provided.

Dockerfile Outdated
--mount=target=/root/.cache,type=cache <<EOT
set -ex
CGO_ENABLED=1 xx-go build -mod=vendor -ldflags '-extldflags -static' -tags 'apparmor seccomp netgo cgo static_build osusergo' -o /usr/bin/runc ./
CGO_ENABLED=1 xx-go build -mod=vendor -ldflags '-extldflags -static' -tags 'apparmor seccomp netgo cgo static_build osusergo runc_nodmz' -o /usr/bin/runc ./
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kolyshkin iiuc building runc-dmz separately and running the go generate before building runc itself is now the recommended way of building runc? When building without runc_nodmz tag with regular go build the runc binary seems to work fine as well, but I guess it is slower? Is the runc-dmz binary itself always throwaway? Is there a recommended way to check that runc was built with optimal dmz?

Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com>
set -ex
if [ -f libcontainer/dmz/_dmz.c ]; then
case "$(xx-info arch)" in
amd64|arm64|s390x|riscv64|386 )
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's not quite the same list as https://github.com/opencontainers/runc/blob/v1.2.0-rc.2/libcontainer/dmz/Makefile#L8 but arm & ppc64le give errors to me. Not sure if Alpine, clang or I'm passing some wrong flags.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant