Skip to content
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

dropNetworking function doesn't compile when building Tekton release #3612

Closed
bobcatfish opened this issue Dec 8, 2020 · 6 comments
Closed
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@bobcatfish
Copy link
Collaborator

In #3582 we added a function that has this code:

	cmd.SysProcAttr.GidMappings = []syscall.SysProcIDMap{
		{
			ContainerID: 0,
			HostID:      0,

			//  Map all groups
			Size: 4294967295,
		},

Unfortunately the value for size is too big for some systems! I guess that the machines we build on must use int32 instead of int64? Not sure exactly but long story short @jerop and I tried to make a release today and when ko ran it errored with:

[publish-images : run-ko]2020/12/08 20:23:14 Unexpected error running "go build": exit status 2
[publish-images : run-ko] # github.com/tektoncd/pipeline/cmd/entrypoint
[publish-images : run-ko] cmd/entrypoint/namespaces_linux.go:32:4: constant 4294967295 overflows int
[publish-images : run-ko] cmd/entrypoint/namespaces_linux.go:47:4: constant 4294967295 overflows int

I'm gonna revert this for now until we can fix it, I dunno if we can just cast the value to int64 or if we need to do something to update the images we build on (maybe both)?

At the very least we should know at PR time that this kind of thing is going to fail so maybe in the long run we can invoke the same Task in our end to end tests :S

@bobcatfish bobcatfish added the kind/bug Categorizes issue or PR as related to a bug. label Dec 8, 2020
bobcatfish added a commit to bobcatfish/pipeline that referenced this issue Dec 8, 2020
…package."

This reverts commit e097c52.

The int used `Size: 4294967295` seems to be too large for the machines
that we build Tekton on! Or too large for int anyway

Opened tektoncd#3612 to figure out a
longer term fix but for now let's revert this to make sure we're in a
releasable state.
tekton-robot pushed a commit that referenced this issue Dec 8, 2020
…package."

This reverts commit e097c52.

The int used `Size: 4294967295` seems to be too large for the machines
that we build Tekton on! Or too large for int anyway

Opened #3612 to figure out a
longer term fix but for now let's revert this to make sure we're in a
releasable state.
@dlorenc
Copy link
Contributor

dlorenc commented Dec 9, 2020

Do you know how this ran? What cluster/task was it in? I'm trying to repro now.

@jerop
Copy link
Member

jerop commented Dec 9, 2020

Do you know how this ran? What cluster/task was it in? I'm trying to repro now.

@dlorenc
Copy link
Contributor

dlorenc commented Dec 9, 2020

Thanks! It looks like this happens because we're cross compiling for 32-bit architectures. We don't currently build that in pre-submit tests. I think that would have to go somewhere in here:
https://github.com/tektoncd/pipeline/blob/master/vendor/github.com/tektoncd/plumbing/scripts/presubmit-tests.sh#L200

@nikhil-thomas
Copy link
Member

nikhil-thomas commented Dec 14, 2020

pre-submit check: build: run ko resolve on build presubmit 🙃 #3621

@bobcatfish shall we close this issue (#3612)

@vdemeester
Copy link
Member

@nikhil-thomas I think we should yes.
/close

@tekton-robot
Copy link
Collaborator

@vdemeester: Closing this issue.

In response to this:

@nikhil-thomas I think we should yes.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

6 participants