- #DOCKER RESTART CONTAINER HOW TO#
- #DOCKER RESTART CONTAINER INSTALL#
- #DOCKER RESTART CONTAINER UPDATE#
Run the install script to set the default content such as roles and permission types sudo su -s /bin/bash -c "/usr/share/php/passbolt/bin/cake passbolt install" www-data Run the install script to install the database tables Make sure the database exists and is accessible for the given database user. Double check the host, database name, username and password in /etc/passbolt/passbolt.php. The application is not able to connect to the database. cURL Error (6) Could not resolve host: *link removed - but it did work with this link* Hostname does not match when validating certificates. Check that the domain name is correct in /etc/passbolt/passbolt.php Could not reach the /healthcheck/status with the url specified in App.fullBaseUrl The passbolt config file is not required if passbolt is configured with environment variables Copy /etc/passbolt/ to /etc/passbolt/passbolt.php The passbolt config file is missing in /etc/passbolt/
The logs directory and its content are writable. The temporary directory and its content are writable and not executable. volume1/docker/passbolt/jwt:/etc/passbolt/jwt:rwĭATASOURCES_DEFAULT_USERNAME: passboltuserĭATASOURCES_DEFAULT_PASSWORD: passboltpassĮMAIL_TRANSPORT_DEFAULT_USERNAME: *removed*ĮMAIL_TRANSPORT_DEFAULT_PASSWORD: *removed*
volume1/docker/passbolt/gpg:/etc/passbolt/gpg:rw usr/bin/wait-for.sh -t 0 db:3306 - /docker-entrypoint.sh Image: passbolt/passbolt:latest-ce-non-root volume1/docker/passbolt/db:/var/lib/mysql:rw
#DOCKER RESTART CONTAINER UPDATE#
Server : Synology NAS, DSM 7.1.1-42962 Update 4
#DOCKER RESTART CONTAINER HOW TO#
I describe the steps on how to reproduce the issue I describe the steps I have taken to trouble shoot the problem I provide a copy of my logs and healthcheck I provide relevant information about my server (component names and versions, etc.) I have read the tutorials, help and searched for similar issues Thanks in advance to anyone who can help. Links in this post have been removed as new users are not allowed more than 2 links in a post. I suspect the problem could be reproduced by installing as above and doing a hard-shutdown (power cut) to the server. The original install was done with this guide : Marius Hosting I have tried stopping all other containers and starting Passbolt on its own with no success (and the same error). I have tried re-starting the container serveral times, always with the same result. I would like to try to resolve this without a full re-install as there are some users who have stored passwords that I would like to retain if possible. I have checked that port 8080 is not being used by another process. The last output from the container is “Failed to connect to localhost port 8080 : Connection refused”. Now the container starts but report it is ‘unhealthy’. The SSL and port forwarding in the router were all working okay. I was able to access Passbolt on the desired subdomain and domain. I have run into a problem where a previously working install of Passbolt in a Docker container on a Synology NAS has stopped working after an unexpected shutdown (due to a power cut) of the server.Įverything was working fine prior to the power cut.
0 kommentar(er)
