BaseAdresseNationale / addok-docker

Conteneurs Addok pour Docker
151 stars 28 forks source link

Addok config file not found! sur Docker Windows 10 #7

Closed louia closed 5 years ago

louia commented 5 years ago

Petit soucis sur Windows 10 quand j'essaie de lancer l'instance j'obtiens :

addok_1 | Addok config file not found! @jdesboeufs Voici mon .yml que j'ai modifié :


services:
  addok:
    image: etalab/addok
    ports:
    - "7878:7878"
    volumes:
    - ./addok-data/addok.conf:/addok.conf
    - ./addok-data/addok.db/addok.db
    - ./logs/logs
    links:
    - addok-redis:redis
    environment:
      WORKERS: 1
      LOG_QUERIES: 1
      LOG_NOT_FOUND: 1
      SLOW_QUERIES: 200
  addok-redis:
    image: etalab/addok-redis
    volumes:
    - ./addok-data/dump.rdb/dump.rdb```
Simon-LePennec commented 4 years ago

Same issue here. I'm using Docker toolbox on Windows 10 (for the 1st time so I may have missed obvious steps) I tried absolute paths and several syntaxes, but I'm not even sure about what I'm supposed to give him

version: '2'

services:
  addok:
    image: etalab/addok
    ports:
    - "7878:7878"
    volumes:
    - ./addok-data/addok.conf:/addok.conf
    - ./addok-data/addok.db:/addok.db
    - ./logs:/logs
    links:
    - addok-redis:redis
    environment:
      WORKERS: 1
      WORKER_TIMEOUT: 30
      LOG_QUERIES: 1
      LOG_NOT_FOUND: 1
      SLOW_QUERIES: 200
  addok-redis:
    image: etalab/addok-redis
    volumes:
    - ./addok-data/dump.rdb:/dump.rdb
$ docker-compose up
Creating network "ban_default" with the default driver
Creating ban_addok-redis_1 ... done                                                                            Creating ban_addok_1       ... done                                                                            Attaching to ban_addok-redis_1, ban_addok_1
addok-redis_1  | 1:C 17 Feb 14:45:00.660 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
addok-redis_1  | 1:C 17 Feb 14:45:00.661 # Redis version=4.0.2, bits=64, commit=00000000, modified=0, pid=1, just started
addok-redis_1  | 1:C 17 Feb 14:45:00.661 # Configuration loaded
addok-redis_1  |                 _._
addok-redis_1  |            _.-``__ ''-._
addok-redis_1  |       _.-``    `.  `_.  ''-._           Redis 4.0.2 (00000000/0) 64 bit
addok-redis_1  |   .-`` .-```.  ```\/    _.,_ ''-._
addok-redis_1  |  (    '      ,       .-`  | `,    )     Running in standalone mode
addok-redis_1  |  |`-._`-...-` __...-.``-._|'` _.-'|     Port: 6379
addok-redis_1  |  |    `-._   `._    /     _.-'    |     PID: 1
addok-redis_1  |   `-._    `-._  `-./  _.-'    _.-'
addok-redis_1  |  |`-._`-._    `-.__.-'    _.-'_.-'|
addok-redis_1  |  |    `-._`-._        _.-'_.-'    |           http://redis.io
addok-redis_1  |   `-._    `-._`-.__.-'_.-'    _.-'
addok-redis_1  |  |`-._`-._    `-.__.-'    _.-'_.-'|
addok-redis_1  |  |    `-._`-._        _.-'_.-'    |
addok-redis_1  |   `-._    `-._`-.__.-'_.-'    _.-'
addok-redis_1  |       `-._    `-.__.-'    _.-'
addok-redis_1  |           `-._        _.-'
addok-redis_1  |               `-.__.-'
addok-redis_1  |
addok-redis_1  | 1:M 17 Feb 14:45:00.665 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
addok-redis_1  | 1:M 17 Feb 14:45:00.666 # Server initialized
addok-redis_1  | 1:M 17 Feb 14:45:00.666 # 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.
addok_1        | Addok config file not found!
ban_addok_1 exited with code 1
Simon-LePennec commented 4 years ago

So it seems the issue may be DockerToolbox. I couldn't solve it, but it worked with Ubunutu and Docker CE.