The docker image does not seem to work on Kubernetes / GCE as currently specified about arangodb-docker HOT 7 CLOSED

I understand your frustration and I hope I have just commited some stuff that addresses most of your issues:

1. The history of this thing is as follows. Initially we did a chown as mysql/postgres are doing. We (I) converted it to this strange rwcheck thing because of docker on mac. Some users wanted to mount foxx apps from their mac into the docker container (which is a perfectly valid usecase). The docker 1.10 setup on mac (using an additional virtual machine) didn't allow chowns because the shared folder stuff that it was using simply failed :(

However assuming correct, writable directories is even worse as you just proved so I have reverted that back to chowns.

I need to check if 1.11 fixes the mac issue. Will do so later.

1. I think the general approach to treat apps and datafiles differentely is ok. I agree that it is a bit more work to handle the 2 volumes but I don't really see a big pain point here.

Assuming a directory layout like this:

/data/postgres
/data/mysql
/data/arangodb/datafiles
/data/arangodb/apps

I can start arangodb using the following volumes:

-v /data/arangodb/datafiles:/var/lib/arangod -v /data/arangodb/apps:/var/lib/arangod-apps

On the host machine I can still simply backup /data

The thing is mysql and postgres don't have any apps but only datafiles.

1. I had a look at mysql and postgres and they are both handling this. I implemented something similar which supports restoring databases and executing javascript

I did my changes currently for the upcoming 3.0 release. Maybe you could have a look at my changes here:

https://github.com/arangodb/arangodb-docker/blob/official/docker-entrypoint3.sh

from arangodb-docker.

The new "native" docker does indeed fix the chown problem :D I think we are done here. Need to discuss with the team about a backport to 2.x as 3.x is very very close

from arangodb-docker.

Hi folks, you say this problem is fixed, but I can't start ArangoDB on Kubernetes backed by docker 1.13.1 with a volume mounted from an NFS storage. Is this due to me using NFS based storage or is the problem sitll around?

from arangodb-docker.

do you think its a clever idea to run a database on an NFS storage in first place?

from arangodb-docker.

Nope! But atm we don't have another opportunity.

from arangodb-docker.

you need a local filesystem for the arangodb data files. Its using mmap to access them, and I don't think that this is supported by the kernel on NFS.

from arangodb-docker.

alright thanks!

from arangodb-docker.