search

ezpaarse-project / ezpaarse

ezPAARSE can ingest your (proxy) log files and show how users access suscribed electronic ressources.
http://www.ezpaarse.org
Other
68 stars 26 forks source link

Docker instructions fail after addition of build #127

Closed ctgraham closed 2 years ago

ctgraham commented 2 years ago

Docker instructions per README: https://github.com/ezpaarse-project/ezpaarse/blob/3.7.2/README.md#use-with-docker Fail after addition of build to docker-compose.yml: https://github.com/ezpaarse-project/ezpaarse/commit/0fc1387d1d42f81934d7f9124740ff27b808039d

[ezpaarse]$ docker-compose up -d
WARNING: The http_proxy variable is not set. Defaulting to a blank string.
WARNING: The https_proxy variable is not set. Defaulting to a blank string.
WARNING: The no_proxy variable is not set. Defaulting to a blank string.
Creating network "ezpaarse_default" with the default driver
Pulling ezpaarse_db (mongo:3.4.1)...
3.4.1: Pulling from library/mongo
5040bd298390: Pull complete
ef697e8d464e: Pull complete
67d7bf010c40: Pull complete
bb0b4f23ca2d: Pull complete
8efff42d23e5: Pull complete
11dec5aa0089: Pull complete
e76feb0ad656: Pull complete
5e1dcc6263a9: Pull complete
2855a823db09: Pull complete
Building ezpaarse
ERROR: Cannot locate specified Dockerfile: Dockerfile

Is it intended to require a git clone or download of the full repository in order to use Docker now?

nojhamster commented 2 years ago

Hi there ! As you noticed, this is a side effect that appeared when we added the build statement, because docker-compose won't download the image automatically if it does not already exist locally. Running docker-compose pull first fixes this issue.

We also added a volume for the config.local.json file, which can prevent the container from starting when the file is missing.

We will update the doc accordingly. Thanks for pointing this out !