Init-configs_1 | cp: can't create './config/': Permission denied doneĪttaching to space-on-premises_init-configs_1 Starting space-on-premises_init-configs_1. I just tried to follow this procedure (as it is also described in the docs) but I get an error message: If any problem occurs, or a process seems to hang, try to docker stop it and successively docker start it. Wait a couple of minutes after the start and then check the results. It may take some time for all Space containers to start properly. Please find the following files in this folder:Ħ) Edit the configurations related to the `altUrls` for Packages, Space, and VCS by adding your IP to the list.ħ) Remove the current installation with the `docker-compose down` command, and then start a new one with `docker-compose up -d`. Note: do this for every docker service definition that references the config object as a Docker volume.ĥ) In step 3, we switched the configuration location to a local config folder that should appear in the Space home directory. Please find the step-by-step instruction below:Ġ) If applicable, stop previously running Space installation.ġ) Navigate to the home Space directory and start editing the `docker-compose.yaml` file.Ģ) Comment the line `config: ` under the volumes section at the bottom of the file.ģ) Change every reference to the docker volume config to `./config`. Hi Jeffrey Watts, you're right, the best way would be to modify and other configuration files.
0 kommentar(er)
