You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When setting a ArangoDB instance up, using arangodb/arangodb-starter and the latest docker image (as is currently the default: ENV DOCKER_IMAGE=arangodb/arangodb:latest in the starter’s Dockerfile), I was surprised to find out that it’s not running it’s base image’s entrypoint.sh — and specifically, the logic one may deposit in docker-entrypoint-initdb.d
We do not use default entrypoints in starter and Operator, due to fact everything inside (mounts, permissions) are managed on starter level. Entrpoints helps you to setup single instance by default, what is not expected by starter.
Hi,
When setting a ArangoDB instance up, using arangodb/arangodb-starter and the latest docker image (as is currently the default:
ENV DOCKER_IMAGE=arangodb/arangodb:latest
in the starter’s Dockerfile), I was surprised to find out that it’s not running it’s base image’s entrypoint.sh — and specifically, the logic one may deposit in docker-entrypoint-initdb.dIs it on purpose?
For now I had to revert to directly using https://github.com/arangodb/arangodb-docker, is there a way I could use starter instead? Should I use starter at all?
Thank you!
The text was updated successfully, but these errors were encountered: