Page History

...

1. Be sure, that user that launches docker container has write permissions on the mounting folders.
2. The version of the Linux kernel version for Ubuntu host machine must be 3.16 or higher (Lower versions contain bug that causes impossibility to use 'su' command in container with '–net=host' option enabled)

3. If you want to start restart docker containers on boot or in case of failure, you should add "–restart=always" option to the run command of container, . The container will not be restarted if it's stopped with "docker kill/stop" command. Here is the example for elasticsearch:

   Code Block
   docker run -p 9200:9200 -p 9300:9300 \ --restart=always \ -v /local_elasticsearch_data_folder:/data \ --net=host \ --name elastic -d practiceinsight/dms_elasticsearch

   If you want to start Nuxeo container on boot then you need to add this option to elasticsearch and postgres containers also.

4.  On Windows mounting folders must be located in C:/Users, on Mac OS X - in /Users 

5. When you are starting the container on Windows, folder must be mounted that way (two slashes are needed for the windows path): 

   Code Block
   -v //c/users/:/path_in_container

6. If you operate docker on Windows with Docker Quickstart Terminal, then execution of the docker exec commands on windows must be done in the docker machine command line. if the docker machine is called "default", then you can get access to it with:

   Code Block
   docker-machine ssh default

   If you operate docker with PowerShell then this step is unnecessary.

...