Your message dated Sun, 27 Jan 2019 23:55:54 +1100
with message-id <4197763.WzzgV0LaB0@deblab>
and subject line Re: [pkg-go] Bug#916256: Bug#916256: Bug#916256: gitlab-runner
fails when it tries to pull docker image gitlab-runner-helper:11.2.0
has caused the Debian Bug report #916256,
regarding gitlab-runner fails when it tries to pull docker image
gitlab-runner-helper:11.2.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
916256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916256
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gitlab-runner
Version: 11.2.0+dfsg-2
Severity: important
Dear Maintainer,
Summary
-------
gitlab-runner executes docker for the first time it tries to download docker
image gitlab-runner-helper:11.2.0
but it fails because repository does not exists with this tag name.
Related links:
* https://hub.docker.com/r/gitlab/gitlab-runner-helper/tags/
Expected behavior
-----------------
gitlab-runner should be able to find the right tag name of gitlab-runner-
helper.
Error
-----
ERRO[0000] Docker executor: prebuilt image helpers will be loaded from
/var/lib/gitlab-runner.
Running with gitlab-runner 11.2.0 (11.2.0)
Using Docker executor with image registry.gitlab.com/<image>:latest ...
Pulling docker image gitlab-runner-helper:11.2.0 ...
ERROR: Job failed: Error response from daemon: pull access denied for gitlab-
runner-helper, repository does not exist or may require 'docker login'
(executor_docker.go:166:1s)
FATAL: Error response from daemon: pull access denied for gitlab-runner-helper,
repository does not exist or may require 'docker login'
(executor_docker.go:166:1s)
Command
-------
$ gitlab-runner exec docker --docker-volumes $PWD/builds:/builds build
Workaround
----------
Download gitlab-runner-helper 11.2.0 version using x86_64-6d9dd510 tag and
rename it locally.
$ docker run --rm -it gitlab/gitlab-runner-helper:x86_64-6d9dd510
$ docker tag gitlab/gitlab-runner-helper:x86_64-6d9dd510 gitlab-runner-
helper:11.2.0
Now you can execute:
$ gitlab-runner exec docker --docker-volumes $PWD/builds:/builds build
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.18.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gitlab-runner depends on:
ii adduser 3.118
ii ca-certificates 20170717
ii git 1:2.19.2-1
ii libc6 2.27-8
ii lsb-base 10.2018112800
Versions of packages gitlab-runner recommends:
ii cdebootstrap 0.7.7+b1
ii xz-utils 5.2.2-1.3
Versions of packages gitlab-runner suggests:
ii docker.io 18.06.1+dfsg1-2
-- Configuration Files:
/etc/gitlab-runner/config.toml [Errno 13] Permission denied:
'/etc/gitlab-runner/config.toml'
-- no debconf information
--- End Message ---
--- Begin Message ---
On Friday, 25 January 2019 4:56:33 PM AEDT Dean Hamstead wrote:
> That said, this error would occur if the kubernetes cluster is external
> to the debian machine that runs the runner? (which is my scenario) as
> that docker instance running on the kubernetes node would not have that
> 'local' image?
Yes, gitlab-runner package produces helper image during post-install stage
and when necessary it is imported into local store for Docker to use.
This would work only when Docker is running by the time when gitlab-runner is
installed because the latter uses "docker build" command to generate helper
image.
> by manually setting the helper_image to something in the gitlab/ space -
> things work for me
Thank you for reporting workaround. It might be useful to some.
> They are ubuntu it seems but they are entirely encapsulated as part of
> the service.
I'm going to close this bug since it is not even about a Debian package which
is probably has been installed improperly... There is nothing I could do
about the package to help with this problem.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
--
Regards,
Dmitry Smirnov.
---
Sometimes the first duty of intelligent men is the restatement of the
obvious.
-- George Orwell
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
_______________________________________________
Pkg-go-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
