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

Jenkinsfile: use "wrappedNode" to set Docker Hub creds #205

Merged
merged 1 commit into from
Nov 30, 2020

Conversation

thaJeztah
Copy link
Member

The "dockereng/rhel" repository is private, so make sure credentials are set.

The "dockereng/rhel" repository is private, so make sure credentials
are set.

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
@thaJeztah
Copy link
Member Author

s390x build still failing; https://ci-next.docker.com/teams-core/blue/rest/organizations/jenkins/pipelines/containerd-packaging/branches/PR-205/runs/2/nodes/60/log/?start=0

I suspect the default user used by wrappedNode (dockerbuildbot) does not have access to that repo;

Building packages on docker.io/dockereng/rhel:7-s390x

containerd   : HEAD (commit: ddb47a3)
runc         : v1.0.0-rc92 (commit: ff819c7)
architecture : s390x
build image  : docker.io/dockereng/rhel:7-s390x
golang image : docker.io/library/golang:1.15.5-buster
--------------------------------------------------------------------
Error response from daemon: pull access denied for dockereng/rhel, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

I think wrappedNode allows passing what credentials to use from Jenkins (through credentialsId ?). We should probably add a PAT to Jenkins that has pull access for that repository, and use that

@thaJeztah
Copy link
Member Author

Interesting; ubuntu:bionic build failed with; https://ci-next.docker.com/teams-core/blue/rest/organizations/jenkins/pipelines/containerd-packaging/branches/PR-205/runs/2/nodes/78/log/?start=0

+ git -C src/github.com/opencontainers/runc fetch --update-head-ok --depth 1 origin refs/tags/v1.0.0-rc92:refs/tags/v1.0.0-rc92
From https://github.com/opencontainers/runc
 * [new tag]         v1.0.0-rc92 -> v1.0.0-rc92
+ git -C src/github.com/opencontainers/runc checkout -q refs/tags/v1.0.0-rc92
./scripts/checkout.sh src/github.com/containerd/containerd "HEAD"
+ SRC=src/github.com/containerd/containerd
+ REF=HEAD
+ REF_FETCH=HEAD
+ awk {print $2}
+ git -C src/github.com/containerd/containerd ls-remote --refs --heads --tags origin HEAD
fatal: unable to access 'https://github.com/containerd/containerd.git/': Problem with the SSL CA cert (path? access rights?)
+ REF=
+ [ -n  ]
+ REF=FETCH_HEAD
+ git -C src/github.com/containerd/containerd fetch --update-head-ok --depth 1 origin HEAD
fatal: unable to access 'https://github.com/containerd/containerd.git/': Problem with the SSL CA cert (path? access rights?)
Makefile:76: recipe for target 'checkout' failed
make[1]: *** [checkout] Error 128
make[1]: Leaving directory '/home/ubuntu/workspace/containerd-packaging_PR-205'
Makefile:72: recipe for target 'docker.io/library/ubuntu:bionic' failed
make: *** [docker.io/library/ubuntu:bionic] Error 2
script returned exit code 2

@thaJeztah
Copy link
Member Author

Some odd errors on ubuntu focal; https://ci-next.docker.com/teams-core/blue/rest/organizations/jenkins/pipelines/containerd-packaging/branches/PR-205/runs/2/nodes/82/log/?start=0

This is on the host:

+ git -C src/github.com/containerd/containerd checkout -q FETCH_HEAD
# upstream systemd unit uses /usr/local/bin, whereas our packages use /usr/bin
sed 's#/usr/local/bin/containerd#/usr/bin/containerd#g' src/github.com/containerd/containerd/containerd.service > common/containerd.service
curl: (77) error setting certificate verify locations:
  CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs

Build also failed, but no idea what the actual failure is;

focal: Pulling from library/ubuntu
Digest: sha256:c95a8e48bf88e9849f3e0f723d9f49fa12c5a00cfc6e60d2bc99d87555295e4c
Status: Image is up to date for ubuntu:focal
docker.io/library/ubuntu:focal
+ DOCKER_BUILDKIT=1 docker build --pull --build-arg GOLANG_IMAGE=docker.io/library/golang:-buster --build-arg BUILD_IMAGE=docker.io/library/ubuntu:focal --build-arg BASE=ubuntu --build-arg CREATE_ARCHIVE=1 --build-arg UID=1000 --build-arg GID=1000 --file=dockerfiles/deb.dockerfile --progress=auto --target=packages --output=. .
#2 [internal] load .dockerignore
#2 transferring context: 145B done
#2 DONE 0.0s

#1 [internal] load build definition from deb.dockerfile
#1 transferring dockerfile: 3.96kB done
#1 DONE 0.0s

#3 resolve image config for docker.io/docker/dockerfile:experimental
#3 DONE 0.3s

#4 docker-image://docker.io/docker/dockerfile:experimental@sha256:de85b2f3a...
#4 resolve docker.io/docker/dockerfile:experimental@sha256:de85b2f3a3e8a2f7fe48e8e84a65f6fdd5cd5183afa6412fff9caa6871649c44 done
#4 sha256:61261561661960014533790f5d6c42f5b88362db7e005f35248c20f075900a61 6.57MB / 8.88MB 0.2s
#4 sha256:de85b2f3a3e8a2f7fe48e8e84a65f6fdd5cd5183afa6412fff9caa6871649c44 1.69kB / 1.69kB done
#4 sha256:8c69d118cfcd040a222bea7f7d57c6156faa938cb61b47657cd65343babc3664 521B / 521B done
#4 sha256:08fb2b2ca3d58e19d791e73dea16126df37608115532e748d63525688df457a5 897B / 897B done
#4 sha256:61261561661960014533790f5d6c42f5b88362db7e005f35248c20f075900a61 8.88MB / 8.88MB 0.3s
#4 sha256:61261561661960014533790f5d6c42f5b88362db7e005f35248c20f075900a61 8.88MB / 8.88MB 0.3s done
#4 extracting sha256:61261561661960014533790f5d6c42f5b88362db7e005f35248c20f075900a61
#4 extracting sha256:61261561661960014533790f5d6c42f5b88362db7e005f35248c20f075900a61 0.4s done
#4 DONE 0.8s
failed to solve with frontend dockerfile.v0: failed to solve with frontend gateway.v0: rpc error: code = Unknown desc = invalid reference format
Makefile:82: recipe for target 'build' failed
make[1]: *** [build] Error 1
make[1]: Leaving directory '/home/ubuntu/workspace/containerd-packaging_PR-205'
Makefile:72: recipe for target 'docker.io/library/ubuntu:focal' failed
make: *** [docker.io/library/ubuntu:focal] Error 2
script returned exit code 2

I assume this output being truncated is just a presentation glitch;

#4 docker-image://docker.io/docker/dockerfile:experimental@sha256:de85b2f3a...

@thaJeztah
Copy link
Member Author

I assume this output being truncated is just a presentation glitch;

Trying on docker 20.10, and I think that's something that's resolved since 19.03 (through moby/buildkit#1435);

#3 resolve image config for docker.io/docker/dockerfile:experimental
#3 sha256:401713457b113a88eb75a6554117f00c1e53f1a15beec44e932157069ae9a9a3
#3 DONE 1.0s

#4 docker-image://docker.io/docker/dockerfile:experimental@sha256:de85b2f3a3e8a2f7fe48e8e84a65f6fdd5cd5183afa6412fff9caa6871649c44
#4 sha256:da233a620f43a1d9f23113b5607b75b09c27f977e1162976b0980c57da4486ce
#4 CACHED

@thaJeztah
Copy link
Member Author

Interesting; Fedora build failed, looks like that machine is using zfs as storage driver?
https://ci-next.docker.com/teams-core/blue/rest/organizations/jenkins/pipelines/containerd-packaging/branches/PR-205/runs/3/nodes/70/log/?start=0

#22 [build-packages 4/4] RUN chown -R 1000:1000 /archive /build
#22 DONE 0.7s

#27 [verify-packages 4/8] COPY --from=build-packages /build/. /build/
#27 ERROR: error creating zfs mount: mount docker-zfs/reolf7omj8lyjsxqzy4ki0z2z:/var/lib/docker/zfs/graph/reolf7omj8lyjsxqzy4ki0z2z: no such file or directory

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.

2 participants