Run installation in sandboxed environment

3liz / lizmap-docker-compose

Run Lizmap stack with docker-compose

30 stars 42 forks source link

Run installation in sandboxed environment #40

Closed dmarteau closed 1 year ago

dmarteau commented 1 year ago

Changes

Remove useless Makefile
Directory configuration run in sandboxed mode using docker container
Update README for running installation

Rational

This leverage the following:

For people that run docker as sudoer it will prevent shooting themselves in the foot with misconfigured install dir (like erasing your system /var directory because INSTALL_DEST was not defined).
Allow install as different user/group even if your are not sudoer but have docker execution rights.

The latter is the most important because it allows separation between admin of the docker stack and the user/group executing services (usually the lizmap user).

nboisteault commented 1 year ago

@nworr Could you test this PR in Windows please?

nworr commented 1 year ago

Got an error :

Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/run/desktop/mnt/host/c/Users/rmartin/Documents/en cours/lizmap-docker-compose-secure-file-mode/lizmap/etc/nginx.conf" to rootfs at "/etc/nginx/nginx.conf": mount /run/desktop/mnt/host/c/Users/rmartin/Documents/en cours/lizmap-docker-compose-secure-file-mode/lizmap/etc/nginx.conf:/etc/nginx/nginx.conf (via /proc/self/fd/14), flags: 0x5000: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

dmarteau commented 1 year ago

@nworr Amha, this is not related to PR, this is when you try to run the docker-compose, you surely have a situation with an already existng install.

Clean up any old installation, run installer, if the install goes ok, check that all files are ok (check nginx.conf). Then try to run the compose stack, which is at this point is not related to this PR.

To make sure, try to install/run from the master branch. If same problem occurs then open a specific issue.

nworr commented 1 year ago

My folder got a space, the configure script was confused, but when i a correct folder name, no more problem launching ngnix

dmarteau commented 1 year ago

@nboisteault @nworr is that ok for you to merge ?

dmarteau commented 1 year ago

@nworr I have made some fixes, could you test one more time on Windows before merging ? thx.

nworr commented 1 year ago

still working, to clarify : i need wsl to launch configure