Skip to content
Snippets Groups Projects
New issue look: Off

Docker develop tag is broken (or just very confusing)

    • Closed Issue created by username-removed-22074 @janpoboril

    I tried to install Docker image gitlab/gitlab-runner:develop, but installation was not smooth:

    DiskStationFryd> docker exec -it gitlab-runner gitlab-runner register
ERRO[0000] Unable to connect to local syslog daemon     
exec: "gitlab-runner": executable file not found in $PATH
Cannot run exec command 79774e395c65eb847fc20225ca8107834944f33354c0fd225268a3c945604cb5 in container 901323516e23c98dd66d121a1ff1dad3a94d8cafa1c6481fea600e9ca93a3651: [8] System error: exec: "gitlab-runner": executable file not found in $PATH
                                           Error starting exec command in container 79774e395c65eb847fc20225ca8107834944f33354c0fd225268a3c945604cb5: Cannot run exec command 79774e395c65eb847fc20225ca8107834944f33354c0fd225268a3c945604cb5 in container 901323516e23c98dd66d121a1ff1dad3a94d8cafa1c6481fea600e9ca93a3651: [8] System error: exec: "gitlab-runner": executable file not found in $PATH

    gitlab-runner is mentioned in instalaltion instructions for Docker

    So I checked README if somethink changed:

    root@gitlab-runner:/go/src/app# cat README.md 
## GitLab Runner

This is the GitLab Runner repository, the official GitLab CI
runner written in Go. It runs tests and sends the results to GitLab CI.
[GitLab CI](https://about.gitlab.com/gitlab-ci) is the open-source
continuous integration server that coordinates the testing.

[![Build Status](https://ci.gitlab.com/projects/1885/status.png?ref=master)](https://ci.gitlab.com/projects/1885?ref=master)

### Contributing

The official repository for this project is on [GitLab.com](https://gitlab.com/gitlab-org/gitlab-ci-multi-runner).

* [Development](docs/development/README.md)
* [Issues](https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/issues)
* [Merge Requests](https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/merge_requests)

### Requirements

**None:** gitlab-ci-multi-runner is run as a single binary.

This project is designed for the Linux, OS X and Windows operating systems.

If you want to use **Docker** make sure that you have **1.5.0** at least installed.

### Features

* Allows to run:
 - multiple jobs concurrently
 - use multiple tokens with multiple server (even per-project)
 - limit number of concurrent jobs per-token
* Jobs can be run:
 - locally
 - using Docker container
 - using Docker container and executing job over SSH
 - connecting to remote SSH server
* Is written in Go and distributed as single binary without any other requirements
* Supports Bash, Windows Batch and Windows PowerShell
* Works on Ubuntu, Debian, OS X and Windows (and anywhere you can run Docker)
* Allows to customize job running environment
* Automatic configuration reload without restart
* Easy to use setup with support for docker, docker-ssh, parallels or ssh running environments
* Enables caching of Docker containers
* Easy installation as service for Linux, OSX and Windows

### Version 0.5.0

Version 0.5.0 introduces many security related changes. 
One of such changes is the different location of `config.toml`.
Previously (prior 0.5.0) config was read from current working directory.
Currently, when `gitlab-runner` is executed by `root` or with `sudo` config is read from `/etc/gitlab-runner/config.toml`.
If `gitlab-runner` is executed by non-root user, the config is read from `$HOME/.gitlab-runner/config.toml`.
However, this doesn't apply to Windows where config is still read from current working directory, but this most likely will change in future.

The config file is automatically migrated when GitLab Runner was installed from GitLab's repository.
**For manual installations the config needs to be moved by hand.**

### Installation

* [Install using GitLab's repository for Debian/Ubuntu/CentOS/RedHat (preferred)](docs/install/linux-repository.md)
* [Install on OSX (preferred)](docs/install/osx.md)
* [Install on Windows (preferred)](docs/install/windows.md)
* [Install as Docker Service](docs/install/docker.md)
* [Manual installation (advanced)](docs/install/linux-manually.md)
* [Bleeding edge (development)](docs/install/bleeding-edge.md)
* [Install development environment](docs/development/README.md)

### Advanced Configuration

* [See advanced configuration options](docs/configuration/advanced-configuration.md)
* [See example configuration file](config.toml.example)
* [See security considerations](docs/security/index.md)

### Example integrations

* [Integrate GitLab CE](docs/examples/gitlab.md)
* [Integrate GitLab CI](docs/examples/gitlab-ci.md)

### Extra projects?

If you want to add another project, token or image simply RE-RUN SETUP.
*You don't have to re-run the runner. It will automatically reload configuration once it changes.*

### Changelog

Visit [Changelog](CHANGELOG.md) to view recent changes.

### Help

```bash
$ gitlab-ci-multi-runner --help
NAME:
   gitlab-ci-multi-runner - a GitLab Runner

USAGE:
   gitlab-ci-multi-runner [global options] command [command options] [arguments...]

VERSION:
   dev

AUTHOR:
  Kamil Trzciński - <ayufan@ayufan.eu>

COMMANDS:
   delete	delete specific runner
   run, r	run multi runner service
   install	install service
   uninstall	uninstall service
   start	start service
   stop		stop service
   restart	restart service
   setup, s	setup a new runner
   run-single	start single runner
   verify	verify all registered runners
   help, h	Shows a list of commands or help for one command

GLOBAL OPTIONS:
   --debug			debug mode [$DEBUG]
   --log-level, -l 'info'	Log level (options: debug, info, warn, error, fatal, panic)
   --help, -h			show help
   --version, -v		print the version

### Future

* It should be simple to add additional executors: DigitalOcean? Amazon EC2?
* Maybe script annotations?

### Author

[Kamil Trzciński](mailto:ayufan@ayufan.eu), 2015, [Polidea](http://www.polidea.com/)

### License

GPLv3

    But there is no command register mentioned in the commands list.

    So I just tried if mentioned binary knows it:

    root@gitlab-runner:/go/src/app# gitlab-ci-multi-runner register
Please enter the gitlab-ci coordinator URL (e.g. http://gitlab-ci.org:3000/):
https://ci.gitlab.com
Please enter the gitlab-ci token for this runner:
xxx
Please enter the gitlab-ci description for this runner:
[gitlab-runner]: xxx
INFO[0425] xxx Registering runner... succeeded     
Please enter the executor: ssh, shell, parallels, docker, docker-ssh:
[shell]: docker
Please enter the Docker image (eg. ruby:2.1):

Please enter the Docker image (eg. ruby:2.1):
alpine         
If you want to enable mysql please enter version (X.Y) or enter latest?

If you want to enable postgres please enter version (X.Y) or enter latest?

If you want to enable redis please enter version (X.Y) or enter latest?

If you want to enable mongo please enter version (X.Y) or enter latest?

INFO[0504] Runner registered successfully. Feel free to start it, but if it's running already the config should be automatically reloaded!

    Heureka! Setup guide is there. But there are some confusing thinks (not huge bug, just UX bug):

    • In first step is in example http://gitlab-ci.org:3000/, but most people maybe use hosted GitLab CI, so why not have in example https://ci.gitlab.com? Who has own installation knows usually what should be there.
    • "Please enter the Docker image" should be "Please enter default the Docker image", shouldn't be?
    • "Feel free to start it, but if it's running..." - It will be better if it tells user if service is running and if not, how to start it.

    And btw, I denied to install any databases in register guide, but on first start it seems like it is there?

    *** WARNING: Service runner-7829984d-project-7481-concurrent-0-mongo probably didn't start properly.

Status code: 139

2015-09-19T06:37:22.183450572Z 2015-09-19T06:37:22.182+0000 I JOURNAL  [initandlisten] journal dir=/data/db/journal
2015-09-19T06:37:22.196065399Z 2015-09-19T06:37:22.183+0000 I JOURNAL  [initandlisten] recover : no journal files present, no recovery needed
2015-09-19T06:37:22.287239911Z 2015-09-19T06:37:22.286+0000 I JOURNAL  [durability] Durability thread started
2015-09-19T06:37:22.287276701Z 2015-09-19T06:37:22.286+0000 I JOURNAL  [journal writer] Journal writer thread started
2015-09-19T06:37:22.291403678Z 2015-09-19T06:37:22.288+0000 I CONTROL  [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/data/db 64-bit host=5cad5cabc5ed
2015-09-19T06:37:22.291430563Z 2015-09-19T06:37:22.288+0000 I CONTROL  [initandlisten] 
2015-09-19T06:37:22.291439750Z 2015-09-19T06:37:22.288+0000 I CONTROL  [initandlisten] ** WARNING: /sys/kernel/mm/transparent_hugepage/enabled is 'always'.
2015-09-19T06:37:22.291447808Z 2015-09-19T06:37:22.288+0000 I CONTROL  [initandlisten] **        We suggest setting it to 'never'
2015-09-19T06:37:22.291454465Z 2015-09-19T06:37:22.288+0000 I CONTROL  [initandlisten] 
2015-09-19T06:37:22.291461103Z 2015-09-19T06:37:22.288+0000 I CONTROL  [initandlisten] ** WARNING: /sys/kernel/mm/transparent_hugepage/defrag is 'always'.
2015-09-19T06:37:22.291468170Z 2015-09-19T06:37:22.288+0000 I CONTROL  [initandlisten] **        We suggest setting it to 'never'
2015-09-19T06:37:22.291474973Z 2015-09-19T06:37:22.288+0000 I CONTROL  [initandlisten] 
2015-09-19T06:37:22.291480986Z 2015-09-19T06:37:22.288+0000 I CONTROL  [initandlisten] db version v3.0.6
2015-09-19T06:37:22.291487025Z 2015-09-19T06:37:22.288+0000 I CONTROL  [initandlisten] git version: 1ef45a23a4c5e3480ac919b28afcba3c615488f2
2015-09-19T06:37:22.291501878Z 2015-09-19T06:37:22.288+0000 I CONTROL  [initandlisten] build info: Linux ip-10-233-162-213 3.2.0-4-amd64 #1 SMP Debian 3.2.46-1 x86_64 BOOST_LIB_VERSION=1_49
2015-09-19T06:37:22.291522243Z 2015-09-19T06:37:22.288+0000 I CONTROL  [initandlisten] allocator: tcmalloc
2015-09-19T06:37:22.291535396Z 2015-09-19T06:37:22.288+0000 I CONTROL  [initandlisten] options: {}
2015-09-19T06:37:22.291541902Z 2015-09-19T06:37:22.289+0000 I INDEX    [initandlisten] allocating new ns file /data/db/local.ns, filling with zeroes...
2015-09-19T06:37:22.345297248Z 2015-09-19T06:37:22.345+0000 I STORAGE  [FileAllocator] allocating new datafile /data/db/local.0, filling with zeroes...
2015-09-19T06:37:22.345495650Z 2015-09-19T06:37:22.345+0000 I STORAGE  [FileAllocator] creating directory /data/db/_tmp
2015-09-19T06:37:22.347008710Z 2015-09-19T06:37:22.346+0000 I STORAGE  [FileAllocator] done allocating datafile /data/db/local.0, size: 64MB,  took 0 secs
2015-09-19T06:37:22.355113239Z 2015-09-19T06:37:22.354+0000 I NETWORK  [initandlisten] waiting for connections on port 27017

*********


*** WARNING: Service runner-7829984d-project-7481-concurrent-0-mysql probably didn't start properly.

Status code: 139

2015-09-19T06:37:17.838022884Z Running mysql_install_db
2015-09-19T06:37:17.965903504Z 2015-09-19 06:37:17 0 [Note] /usr/sbin/mysqld (mysqld 5.6.26) starting as process 15 ...
2015-09-19T06:37:17.978892449Z 2015-09-19 06:37:17 15 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-09-19T06:37:17.982203957Z 2015-09-19 06:37:17 15 [Note] InnoDB: The InnoDB memory heap is disabled
2015-09-19T06:37:17.982251460Z 2015-09-19 06:37:17 15 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-09-19T06:37:17.982276154Z 2015-09-19 06:37:17 15 [Note] InnoDB: Memory barrier is not used
2015-09-19T06:37:17.982294057Z 2015-09-19 06:37:17 15 [Note] InnoDB: Compressed tables use zlib 1.2.7
2015-09-19T06:37:17.982308137Z 2015-09-19 06:37:17 15 [Note] InnoDB: Using Linux native AIO
2015-09-19T06:37:17.982320834Z 2015-09-19 06:37:17 15 [Note] InnoDB: Using CPU crc32 instructions
2015-09-19T06:37:17.996737186Z 2015-09-19 06:37:17 15 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-09-19T06:37:18.009995282Z 2015-09-19 06:37:18 15 [Note] InnoDB: Completed initialization of buffer pool
2015-09-19T06:37:18.046304370Z 2015-09-19 06:37:18 15 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
2015-09-19T06:37:18.046610247Z 2015-09-19 06:37:18 15 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
2015-09-19T06:37:18.046969061Z 2015-09-19 06:37:18 15 [Note] InnoDB: Database physically writes the file full: wait...
2015-09-19T06:37:18.133120340Z 2015-09-19 06:37:18 15 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
2015-09-19T06:37:18.469578764Z 2015-09-19 06:37:18 15 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
2015-09-19T06:37:18.817835462Z 2015-09-19 06:37:18 15 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2015-09-19T06:37:18.819670936Z 2015-09-19 06:37:18 15 [Warning] InnoDB: New log files created, LSN=45781
2015-09-19T06:37:18.819715473Z 2015-09-19 06:37:18 15 [Note] InnoDB: Doublewrite buffer not found: creating new
2015-09-19T06:37:18.844232903Z 2015-09-19 06:37:18 15 [Note] InnoDB: Doublewrite buffer created
2015-09-19T06:37:18.857697103Z 2015-09-19 06:37:18 15 [Note] InnoDB: 128 rollback segment(s) are active.
2015-09-19T06:37:18.857729484Z 2015-09-19 06:37:18 15 [Warning] InnoDB: Creating foreign key constraint system tables.
2015-09-19T06:37:18.860821845Z 2015-09-19 06:37:18 15 [Note] InnoDB: Foreign key constraint system tables created
2015-09-19T06:37:18.860839447Z 2015-09-19 06:37:18 15 [Note] InnoDB: Creating tablespace and datafile system tables.
2015-09-19T06:37:18.862299463Z 2015-09-19 06:37:18 15 [Note] InnoDB: Tablespace and datafile system tables created.
2015-09-19T06:37:18.862402576Z 2015-09-19 06:37:18 15 [Note] InnoDB: Waiting for purge to start
2015-09-19T06:37:18.919829883Z 2015-09-19 06:37:18 15 [Note] InnoDB: 5.6.26 started; log sequence number 0
2015-09-19T06:37:19.247599451Z 2015-09-19 06:37:19 15 [Note] Binlog end
2015-09-19T06:37:19.247966822Z 2015-09-19 06:37:19 15 [Note] InnoDB: FTS optimize thread exiting.
2015-09-19T06:37:19.248387320Z 2015-09-19 06:37:19 15 [Note] InnoDB: Starting shutdown...
2015-09-19T06:37:20.768096170Z 2015-09-19 06:37:20 15 [Note] InnoDB: Shutdown completed; log sequence number 1625977
2015-09-19T06:37:20.772299069Z 
2015-09-19T06:37:20.772382929Z 
2015-09-19T06:37:20.793665105Z 2015-09-19 06:37:20 0 [Note] /usr/sbin/mysqld (mysqld 5.6.26) starting as process 38 ...
2015-09-19T06:37:20.798490815Z 2015-09-19 06:37:20 38 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-09-19T06:37:20.798558296Z 2015-09-19 06:37:20 38 [Note] InnoDB: The InnoDB memory heap is disabled
2015-09-19T06:37:20.798595080Z 2015-09-19 06:37:20 38 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-09-19T06:37:20.798647377Z 2015-09-19 06:37:20 38 [Note] InnoDB: Memory barrier is not used
2015-09-19T06:37:20.798682306Z 2015-09-19 06:37:20 38 [Note] InnoDB: Compressed tables use zlib 1.2.7
2015-09-19T06:37:20.798806642Z 2015-09-19 06:37:20 38 [Note] InnoDB: Using Linux native AIO
2015-09-19T06:37:20.799124880Z 2015-09-19 06:37:20 38 [Note] InnoDB: Using CPU crc32 instructions
2015-09-19T06:37:20.800946642Z 2015-09-19 06:37:20 38 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-09-19T06:37:20.809915632Z 2015-09-19 06:37:20 38 [Note] InnoDB: Completed initialization of buffer pool
2015-09-19T06:37:20.836160657Z 2015-09-19 06:37:20 38 [Note] InnoDB: Highest supported file format is Barracuda.
2015-09-19T06:37:20.890876711Z 2015-09-19 06:37:20 38 [Note] InnoDB: 128 rollback segment(s) are active.
2015-09-19T06:37:20.910528619Z 2015-09-19 06:37:20 38 [Note] InnoDB: Waiting for purge to start
2015-09-19T06:37:20.941403398Z 2015-09-19 06:37:20 38 [Note] InnoDB: 5.6.26 started; log sequence number 1625977
2015-09-19T06:37:21.455246192Z 2015-09-19 06:37:21 38 [Note] Binlog end
2015-09-19T06:37:21.463195406Z 2015-09-19 06:37:21 38 [Note] InnoDB: FTS optimize thread exiting.
2015-09-19T06:37:21.463232601Z 2015-09-19 06:37:21 38 [Note] InnoDB: Starting shutdown...
2015-09-19T06:37:22.705844231Z 2015-09-19 06:37:22 38 [Note] InnoDB: Shutdown completed; log sequence number 1625987
2015-09-19T06:37:22.709677109Z 
2015-09-19T06:37:22.709697707Z 
2015-09-19T06:37:22.709704987Z 
2015-09-19T06:37:22.709711339Z 
2015-09-19T06:37:22.709718662Z PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
2015-09-19T06:37:22.709725349Z To do so, start the server, then issue the following commands:
2015-09-19T06:37:22.709731537Z 
2015-09-19T06:37:22.709737426Z   /usr/bin/mysqladmin -u root password 'new-password'
2015-09-19T06:37:22.709743454Z   /usr/bin/mysqladmin -u root -h b1a8c0659865 password 'new-password'
2015-09-19T06:37:22.709749492Z 
2015-09-19T06:37:22.709755499Z Alternatively you can run:
2015-09-19T06:37:22.709783656Z 
2015-09-19T06:37:22.709792004Z   /usr/bin/mysql_secure_installation
2015-09-19T06:37:22.709798163Z 
2015-09-19T06:37:22.709804043Z which will also give you the option of removing the test
2015-09-19T06:37:22.709810143Z databases and anonymous user created by default.  This is
2015-09-19T06:37:22.709816328Z strongly recommended for production servers.
2015-09-19T06:37:22.709822283Z 
2015-09-19T06:37:22.709827854Z See the manual for more instructions.
2015-09-19T06:37:22.709833791Z 
2015-09-19T06:37:22.709839579Z Please report any problems at http://bugs.mysql.com/
2015-09-19T06:37:22.709845573Z 
2015-09-19T06:37:22.709851516Z The latest information about MySQL is available on the web at
2015-09-19T06:37:22.709866761Z 
2015-09-19T06:37:22.709872798Z   http://www.mysql.com
2015-09-19T06:37:22.709878694Z 
2015-09-19T06:37:22.709884648Z Support MySQL by buying support/licenses at http://shop.mysql.com
2015-09-19T06:37:22.709890933Z 
2015-09-19T06:37:22.709896703Z Note: new default config file not created.
2015-09-19T06:37:22.709902656Z Please make sure your config file is current
2015-09-19T06:37:22.709908518Z 
2015-09-19T06:37:22.709914209Z WARNING: Default config file /etc/mysql/my.cnf exists on the system
2015-09-19T06:37:22.709920368Z This file will be read by default by the MySQL server
2015-09-19T06:37:22.709926251Z If you do not want to use this, either remove it, or use the
2015-09-19T06:37:22.709932434Z --defaults-file argument to mysqld_safe when starting the server
2015-09-19T06:37:22.709938374Z 
2015-09-19T06:37:22.712720005Z Finished mysql_install_db
2015-09-19T06:37:22.727664287Z MySQL init process in progress...
2015-09-19T06:37:23.758400947Z MySQL init process in progress...
2015-09-19T06:37:24.014501072Z 2015-09-19 06:37:24 0 [Note] mysqld (mysqld 5.6.26) starting as process 61 ...
2015-09-19T06:37:24.025071474Z 2015-09-19 06:37:24 61 [Note] Plugin 'FEDERATED' is disabled.
2015-09-19T06:37:24.035185640Z 2015-09-19 06:37:24 61 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-09-19T06:37:24.035222978Z 2015-09-19 06:37:24 61 [Note] InnoDB: The InnoDB memory heap is disabled
2015-09-19T06:37:24.035230355Z 2015-09-19 06:37:24 61 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-09-19T06:37:24.035254041Z 2015-09-19 06:37:24 61 [Note] InnoDB: Memory barrier is not used
2015-09-19T06:37:24.035264534Z 2015-09-19 06:37:24 61 [Note] InnoDB: Compressed tables use zlib 1.2.7
2015-09-19T06:37:24.035271248Z 2015-09-19 06:37:24 61 [Note] InnoDB: Using Linux native AIO
2015-09-19T06:37:24.035277175Z 2015-09-19 06:37:24 61 [Note] InnoDB: Using CPU crc32 instructions
2015-09-19T06:37:24.035291181Z 2015-09-19 06:37:24 61 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-09-19T06:37:24.100461526Z 2015-09-19 06:37:24 61 [Note] InnoDB: Completed initialization of buffer pool
2015-09-19T06:37:24.123354134Z 2015-09-19 06:37:24 61 [Note] InnoDB: Highest supported file format is Barracuda.
2015-09-19T06:37:24.264370266Z 2015-09-19 06:37:24 61 [Note] InnoDB: 128 rollback segment(s) are active.
2015-09-19T06:37:24.303608665Z 2015-09-19 06:37:24 61 [Note] InnoDB: Waiting for purge to start
2015-09-19T06:37:24.303650692Z 2015-09-19 06:37:24 61 [Note] InnoDB: 5.6.26 started; log sequence number 1625987
2015-09-19T06:37:24.303659348Z 2015-09-19 06:37:24 61 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: e30dd507-5e98-11e5-b660-0242ac113d97.
2015-09-19T06:37:24.303682230Z 2015-09-19 06:37:24 61 [Warning] 'user' entry 'root@b1a8c0659865' ignored in --skip-name-resolve mode.
2015-09-19T06:37:24.303689417Z 2015-09-19 06:37:24 61 [Warning] 'user' entry '@b1a8c0659865' ignored in --skip-name-resolve mode.
2015-09-19T06:37:24.303696208Z 2015-09-19 06:37:24 61 [Warning] 'proxies_priv' entry '@ root@b1a8c0659865' ignored in --skip-name-resolve mode.
2015-09-19T06:37:24.303703310Z 2015-09-19 06:37:24 61 [Note] Event Scheduler: Loaded 0 events
2015-09-19T06:37:24.303709231Z 2015-09-19 06:37:24 61 [Note] mysqld: ready for connections.
2015-09-19T06:37:24.303714980Z Version: '5.6.26'  socket: '/var/run/mysqld/mysqld.sock'  port: 0  MySQL Community Server (GPL)

*********


*** WARNING: Service runner-7829984d-project-7481-concurrent-0-postgres probably didn't start properly.

Status code: 139

2015-09-19T06:37:19.161537607Z The files belonging to this database system will be owned by user "postgres".
2015-09-19T06:37:19.161607899Z This user must also own the server process.
2015-09-19T06:37:19.161617382Z 
2015-09-19T06:37:19.161623982Z The database cluster will be initialized with locale "en_US.utf8".
2015-09-19T06:37:19.161630346Z The default database encoding has accordingly been set to "UTF8".
2015-09-19T06:37:19.161637262Z The default text search configuration will be set to "english".
2015-09-19T06:37:19.161643247Z 
2015-09-19T06:37:19.161665782Z Data page checksums are disabled.
2015-09-19T06:37:19.161671617Z 
2015-09-19T06:37:19.161677477Z fixing permissions on existing directory /var/lib/postgresql/data ... ok
2015-09-19T06:37:19.164976940Z creating subdirectories ... ok
2015-09-19T06:37:19.230012126Z selecting default max_connections ... 100
2015-09-19T06:37:19.247367271Z selecting default shared_buffers ... 128MB
2015-09-19T06:37:19.247412634Z selecting dynamic shared memory implementation ... posix
2015-09-19T06:37:19.714222921Z creating configuration files ... ok
2015-09-19T06:37:20.841417654Z creating template1 database in /var/lib/postgresql/data/base/1 ... ok
2015-09-19T06:37:20.921626009Z initializing pg_authid ... ok
2015-09-19T06:37:21.038054417Z initializing dependencies ... ok
2015-09-19T06:37:21.334364348Z creating system views ... ok
2015-09-19T06:37:21.479284087Z loading system objects' descriptions ... ok
2015-09-19T06:37:21.713688610Z creating collations ... ok
2015-09-19T06:37:21.764972604Z creating conversions ... ok
2015-09-19T06:37:21.828627951Z creating dictionaries ... ok
2015-09-19T06:37:21.848818574Z setting privileges on built-in objects ... ok
2015-09-19T06:37:22.238130680Z creating information schema ... ok
2015-09-19T06:37:22.277750247Z loading PL/pgSQL server-side language ... ok
2015-09-19T06:37:22.636675380Z vacuuming database template1 ... ok
2015-09-19T06:37:22.695397635Z copying template1 to template0 ... ok
2015-09-19T06:37:22.759266507Z copying template1 to postgres ... ok
2015-09-19T06:37:22.866983680Z syncing data to disk ... ok
2015-09-19T06:37:22.867097181Z 
2015-09-19T06:37:22.867112144Z WARNING: enabling "trust" authentication for local connections
2015-09-19T06:37:22.867119584Z You can change this by editing pg_hba.conf or using the option -A, or
2015-09-19T06:37:22.867125901Z --auth-local and --auth-host, the next time you run initdb.
2015-09-19T06:37:22.867168583Z 
2015-09-19T06:37:22.867179924Z Success. You can now start the database server using:
2015-09-19T06:37:22.867186163Z 
2015-09-19T06:37:22.867207560Z     postgres -D /var/lib/postgresql/data
2015-09-19T06:37:22.867250959Z or
2015-09-19T06:37:22.867419633Z     pg_ctl -D /var/lib/postgresql/data -l logfile start
2015-09-19T06:37:22.867435841Z 
2015-09-19T06:37:22.870679679Z ****************************************************
2015-09-19T06:37:22.870697987Z WARNING: No password has been set for the database.
2015-09-19T06:37:22.870704928Z          This will allow anyone with access to the
2015-09-19T06:37:22.870711052Z          Postgres port to access your database. In
2015-09-19T06:37:22.870716585Z          Docker's default configuration, this is
2015-09-19T06:37:22.870722269Z          effectively any other container on the same
2015-09-19T06:37:22.870728000Z          system.
2015-09-19T06:37:22.870733900Z 
2015-09-19T06:37:22.870739285Z          Use "-e POSTGRES_PASSWORD=password" to set
2015-09-19T06:37:22.870757725Z          it in "docker run".
2015-09-19T06:37:22.870764063Z ****************************************************
2015-09-19T06:37:22.917578947Z waiting for server to start....LOG:  database system was shut down at 2015-09-19 06:37:22 UTC
2015-09-19T06:37:22.919764500Z LOG:  MultiXact member wraparound protections are now enabled
2015-09-19T06:37:22.921936904Z LOG:  database system is ready to accept connections
2015-09-19T06:37:22.922671486Z LOG:  autovacuum launcher started
2015-09-19T06:37:23.909005297Z  done
2015-09-19T06:37:23.909070384Z server started
2015-09-19T06:37:24.016770418Z ALTER ROLE
2015-09-19T06:37:24.026032230Z 
2015-09-19T06:37:24.026056077Z 
2015-09-19T06:37:24.026063289Z /docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
2015-09-19T06:37:24.026069835Z 
2015-09-19T06:37:24.100546786Z waiting for server to shut down...LOG:  received fast shutdown request
2015-09-19T06:37:24.100566813Z LOG:  aborting any active transactions
2015-09-19T06:37:24.100573651Z .LOG:  autovacuum launcher shutting down
2015-09-19T06:37:24.100579608Z LOG:  shutting down
2015-09-19T06:37:24.116591750Z LOG:  database system is shut down

*********


*** WARNING: Service runner-7829984d-project-7481-concurrent-0-redis probably didn't start properly.

Status code: 139

2015-09-19T06:37:20.488990021Z 1:C 19 Sep 06:37:20.480 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
2015-09-19T06:37:20.489139839Z                 _._                                                  
2015-09-19T06:37:20.489162713Z            _.-``__ ''-._                                             
2015-09-19T06:37:20.489193473Z       _.-``    `.  `_.  ''-._           Redis 3.0.3 (00000000/0) 64 bit
2015-09-19T06:37:20.489215890Z   .-`` .-```.  ```\/    _.,_ ''-._                                   
2015-09-19T06:37:20.489228381Z  (    '      ,       .-`  | `,    )     Running in standalone mode
2015-09-19T06:37:20.489240793Z  |`-._`-...-` __...-.``-._|'` _.-'|     Port: 6379
2015-09-19T06:37:20.489252408Z  |    `-._   `._    /     _.-'    |     PID: 1
2015-09-19T06:37:20.489276379Z   `-._    `-._  `-./  _.-'    _.-'                                   
2015-09-19T06:37:20.489288528Z  |`-._`-._    `-.__.-'    _.-'_.-'|                                  
2015-09-19T06:37:20.489300185Z  |    `-._`-._        _.-'_.-'    |           http://redis.io        
2015-09-19T06:37:20.489311747Z   `-._    `-._`-.__.-'_.-'    _.-'                                   
2015-09-19T06:37:20.489323025Z  |`-._`-._    `-.__.-'    _.-'_.-'|                                  
2015-09-19T06:37:20.489334039Z  |    `-._`-._        _.-'_.-'    |                                  
2015-09-19T06:37:20.489345633Z   `-._    `-._`-.__.-'_.-'    _.-'                                   
2015-09-19T06:37:20.489356699Z       `-._    `-.__.-'    _.-'                                       
2015-09-19T06:37:20.489370270Z           `-._        _.-'                                           
2015-09-19T06:37:20.489381970Z               `-.__.-'                                               
2015-09-19T06:37:20.489392805Z 
2015-09-19T06:37:20.489403633Z 1:M 19 Sep 06:37:20.486 # Server started, Redis version 3.0.3
2015-09-19T06:37:20.489415099Z 1:M 19 Sep 06:37:20.486 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
2015-09-19T06:37:20.489459445Z 1:M 19 Sep 06:37:20.486 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
2015-09-19T06:37:20.489476331Z 1:M 19 Sep 06:37:20.486 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
2015-09-19T06:37:20.489492667Z 1:M 19 Sep 06:37:20.486 * The server is now ready to accept connections on port 6379

    It is just feedback, I hope useful for you :-)

    Designs

      Child items ...

      2. Activity

      Please register or sign in to reply