## Summary In my company we want to keep all needed images within our private Docker registry. I've noticed, that if I pull an image from Docker Hub, push it to our registry, after using it in .gitlab-ci.yml file - I'm getting strange "verbose" (actually... service logs from container). That's not a case if I'm using the "official" images in GitLab CI YAML. ## Steps to reproduce ```bash docker pull mariadb:10.2 docker image tag mariadb:10.2 registry.yoda/mariadb:10.2 docker image push registry.yoda/mariadb:10.2 ``` Then use *registry.yoda/mariadb:10.2* in .gitlab-ci.yml file as a service. ## Actual behavior I'm getting full verbose output (containing startup logs of service - MariaDB in this case) which in the end causes **exit code 1** to appear. The container however is up and running. ## Expected behavior Same as actual behavior, but without verbose messages and with correct exit code (without warning about not proper service startup). ## Relevant logs and/or screenshots ***.gitlab-ci.yml (correct, without verbosity):*** ```yml services: - name: mariadb:10.2 alias: mariadb ``` ***.gitlab-ci.yml (wrong, verbose & warning):*** ```yml services: - name: registry.yoda/mariadb:10.2 alias: mariadb ``` ***GitLab Runner output for "wrong" config:*** ```bash Running with gitlab-runner 10.6.0 (a3543a27) on Yoda 42700a6e Using Docker executor with image registry.yoda/php:7.1 ... Starting service registry.yoda/mariadb:10.2 ... Pulling docker image registry.yoda/mariadb:10.2 ... Using docker image sha256:6d67641a058d62d9285a9c4a59e143b63b8366f8e2508f090ce428f0d0c881b3 for registry.yoda/mariadb:10.2 ... Starting service selenium/standalone-chrome:latest ... Pulling docker image selenium/standalone-chrome:latest ... Using docker image sha256:e0ce273809e5c591721f56897140d191056c15fff66b58c7c76e500213c07d66 for selenium/standalone-chrome:latest ... Waiting for services to be up and running... *** WARNING: Service runner-42700a6e-project-56-concurrent-0-registry.yoda__mariadb-0 probably didn't start properly. exit code 1 2018-03-26T08:32:53.195672409Z Initializing database 2018-03-26T08:33:00.724371025Z 2018-03-26T08:33:00.724413898Z PLEASE REMEMBER TO SET A PASSWORD FOR THE MariaDB root USER ! 2018-03-26T08:33:00.724426638Z To do so, start the server, then issue the following commands: 2018-03-26T08:33:00.724434144Z 2018-03-26T08:33:00.724440870Z '/usr/bin/mysqladmin' -u root password 'new-password' 2018-03-26T08:33:00.724447977Z '/usr/bin/mysqladmin' -u root -h password 'new-password' 2018-03-26T08:33:00.724455095Z 2018-03-26T08:33:00.724461738Z Alternatively you can run: 2018-03-26T08:33:00.724472366Z '/usr/bin/mysql_secure_installation' 2018-03-26T08:33:00.724483228Z 2018-03-26T08:33:00.724502779Z which will also give you the option of removing the test 2018-03-26T08:33:00.724513625Z databases and anonymous user created by default. This is 2018-03-26T08:33:00.724524578Z strongly recommended for production servers. 2018-03-26T08:33:00.724535356Z 2018-03-26T08:33:00.724545775Z See the MariaDB Knowledgebase at http://mariadb.com/kb or the 2018-03-26T08:33:00.724556629Z MySQL manual for more instructions. 2018-03-26T08:33:00.724567213Z 2018-03-26T08:33:00.724578413Z Please report any problems at http://mariadb.org/jira 2018-03-26T08:33:00.724589444Z 2018-03-26T08:33:00.724608499Z The latest information about MariaDB is available at http://mariadb.org/. 2018-03-26T08:33:00.724619189Z You can find additional information about the MySQL part at: 2018-03-26T08:33:00.724629875Z http://dev.mysql.com 2018-03-26T08:33:00.724640236Z Consider joining MariaDB's strong and vibrant community: 2018-03-26T08:33:00.724651350Z https://mariadb.org/get-involved/ 2018-03-26T08:33:00.724662234Z 2018-03-26T08:33:00.724675344Z Database initialized 2018-03-26T08:33:00.899671657Z MySQL init process in progress... 2018-03-26T08:33:01.013223474Z 2018-03-26 8:33:01 140442186831744 [Note] mysqld (mysqld 10.2.13-MariaDB-10.2.13+maria~jessie) starting as process 100 ... 2018-03-26T08:33:01.026918189Z 2018-03-26 8:33:01 140442186831744 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-03-26T08:33:01.026949262Z 2018-03-26 8:33:01 140442186831744 [Note] InnoDB: Uses event mutexes 2018-03-26T08:33:01.026957011Z 2018-03-26 8:33:01 140442186831744 [Note] InnoDB: Compressed tables use zlib 1.2.8 2018-03-26T08:33:01.026963044Z 2018-03-26 8:33:01 140442186831744 [Note] InnoDB: Using Linux native AIO 2018-03-26T08:33:01.027061462Z 2018-03-26 8:33:01 140442186831744 [Note] InnoDB: Number of pools: 1 2018-03-26T08:33:01.027115930Z 2018-03-26 8:33:01 140442186831744 [Note] InnoDB: Using SSE2 crc32 instructions 2018-03-26T08:33:01.028000926Z 2018-03-26 8:33:01 140442186831744 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M 2018-03-26T08:33:01.035720004Z 2018-03-26 8:33:01 140442186831744 [Note] InnoDB: Completed initialization of buffer pool 2018-03-26T08:33:01.038013064Z 2018-03-26 8:33:01 140441450923776 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2018-03-26T08:33:01.086206947Z 2018-03-26 8:33:01 140442186831744 [Note] InnoDB: Highest supported file format is Barracuda. 2018-03-26T08:33:01.411776021Z 2018-03-26 8:33:01 140442186831744 [Note] InnoDB: 128 out of 128 rollback segments are active. 2018-03-26T08:33:01.412068466Z 2018-03-26 8:33:01 140442186831744 [Note] InnoDB: Creating shared tablespace for temporary tables 2018-03-26T08:33:01.435988319Z 2018-03-26 8:33:01 140442186831744 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2018-03-26T08:33:01.436097200Z 2018-03-26 8:33:01 140442186831744 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2018-03-26T08:33:01.441913188Z 2018-03-26 8:33:01 140442186831744 [Note] InnoDB: 5.7.21 started; log sequence number 1619996 2018-03-26T08:33:01.442440692Z 2018-03-26 8:33:01 140441286579968 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2018-03-26T08:33:01.452811280Z 2018-03-26 8:33:01 140442186831744 [Note] Plugin 'FEEDBACK' is disabled. 2018-03-26T08:33:01.527995798Z 2018-03-26 8:33:01 140441286579968 [Note] InnoDB: Buffer pool(s) load completed at 180326 8:33:01 2018-03-26T08:33:01.746045625Z 2018-03-26 8:33:01 140442186831744 [Warning] 'user' entry 'root@84725e8f50c0' ignored in --skip-name-resolve mode. 2018-03-26T08:33:01.746083264Z 2018-03-26 8:33:01 140442186831744 [Warning] 'proxies_priv' entry '@% root@84725e8f50c0' ignored in --skip-name-resolve mode. 2018-03-26T08:33:01.883339524Z 2018-03-26 8:33:01 140442186831744 [Note] Reading of all Master_info entries succeded 2018-03-26T08:33:01.883395639Z 2018-03-26 8:33:01 140442186831744 [Note] Added new Master_info '' to hash table 2018-03-26T08:33:01.883410890Z 2018-03-26 8:33:01 140442186831744 [Note] mysqld: ready for connections. 2018-03-26T08:33:01.883422940Z Version: '10.2.13-MariaDB-10.2.13+maria~jessie' socket: '/var/run/mysqld/mysqld.sock' port: 0 mariadb.org binary distribution 2018-03-26T08:33:02.318166727Z Warning: Unable to load '/usr/share/zoneinfo/leap-seconds.list' as time zone. Skipping it. 2018-03-26T08:33:03.911576417Z 2018-03-26 8:33:03 140442012219136 [Warning] 'proxies_priv' entry '@% root@84725e8f50c0' ignored in --skip-name-resolve mode. 2018-03-26T08:33:03.923187113Z 2018-03-26T08:33:03.923466915Z 2018-03-26 8:33:03 140442011916032 [Note] mysqld (unknown): Normal shutdown 2018-03-26T08:33:03.923647037Z 2018-03-26 8:33:03 140442011916032 [Note] Event Scheduler: Purging the queue. 0 events 2018-03-26T08:33:03.923785545Z 2018-03-26 8:33:03 140441328543488 [Note] InnoDB: FTS optimize thread exiting. 2018-03-26T08:33:04.089569042Z 2018-03-26 8:33:04 140442011916032 [Note] InnoDB: Starting shutdown... 2018-03-26T08:33:04.090841774Z 2018-03-26 8:33:04 140441286579968 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool 2018-03-26T08:33:04.091150583Z 2018-03-26 8:33:04 140441286579968 [Note] InnoDB: Buffer pool(s) dump completed at 180326 8:33:04 ********* Pulling docker image registry.yoda/php:7.1 ... Using docker image sha256:a53023961619735a0bfdd55a9f8da6867aa009a8cc4a151a8985ffddcf989903 for registry.yoda/php:7.1 ... Running on docker via yoda... Fetching changes... Removing composer.lock Removing vendor HEAD is now at 47207ec57 GitLab CI integration Checking out 47207ec5 as gitlab... Skipping Git submodules setup $ exit 0 Job succeeded ``` ## Environment description I'm using custom installation of GitLab. GitLab Runner is installed from package repository on Debian 9 (https://docs.gitlab.com/runner/install/linux-repository.html). I'm using Docker executors. Docker Registry is running on the same machine ```bash docker info ``` ```bash Containers: 9 Running: 1 Paused: 0 Stopped: 8 Images: 441 Server Version: 18.03.0-ce Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Native Overlay Diff: true Logging Driver: json-file Cgroup Driver: cgroupfs Plugins: Volume: local Network: bridge host macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog Swarm: inactive Runtimes: runc Default Runtime: runc Init Binary: docker-init containerd version: cfd04396dc68220d1cecbe686a6cc3aa5ce3667c runc version: 4fc53a81fb7c994640722ac585fa9ca548971871 init version: 949e6fa Security Options: seccomp Profile: default Kernel Version: 4.9.0-6-amd64 Operating System: Debian GNU/Linux 9 (stretch) OSType: linux Architecture: x86_64 CPUs: 4 Total Memory: 7.759GiB Name: yoda ID: A5W3:KHZV:IWAB:EKQH:OY3T:RYSI:GF26:DCQN:TC3L:Z4MT:BQDG:WSJU Docker Root Dir: /var/lib/docker Debug Mode (client): false Debug Mode (server): false Registry: https://index.docker.io/v1/ Labels: Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false WARNING: No swap limit support ``` ### Used GitLab Runner version ```bash Version: 10.6.0 Git revision: a3543a27 Git branch: 10-6-stable GO version: go1.9.4 Built: 2018-03-22T08:34:11+00:00 OS/Arch: linux/amd64 ```