Closed wenshutang closed 6 years ago
Hi, we run https://github.com/arangodb/arangodb-docker/tree/official/test-user-scripts on each push of the docker container. Please have a look at them, whether they can serve as a working example for you.
@dothebart Thank you for the information. The scripts I have run fine on an arangodb container, it's when I try to bring it up using docker-compose that I am having issues. The entrypoint.sh
script doesn't seem to run at all, I don't even see these 2 lines:
Initializing database...Hang on...
Database initialized...Starting System...
I had exactly the same problem using docker-compose. I removed all of my containers and images and then tried again, this time it imported my /dumps
could it be related to this comment? https://github.com/docker-library/postgres/issues/203#issuecomment-255200501 (learned that from @rtmruczek )
Yes, see my previous comment
Yes @dothebart @brendanwheble, I believe this caused by persistence, much like the postgres issue
I believe this line in the docker entry file is the root cause. Try removing the file /var/lib/arangodb3/SERVER
ok, maybe https://github.com/arangodb/arangodb-docker/pull/51 would then better help to see why no initialisation is done.
Ok, the current arangodb docker containers now contain these hints, will close this issue.
We run a few scripts inside /docker-entrypoint-initdb.d When using docker to run the container, the scripts run fine:
But when using docker-compose, the scripts are skipped
Part of my compose file:
Is there anything I am missing here? Why the inconsistency?