MAJ terminée. Nous sommes passés en version 14.6.2 . Pour consulter les "releases notes" associées c'est ici :

https://about.gitlab.com/releases/2022/01/11/security-release-gitlab-14-6-2-released/
https://about.gitlab.com/releases/2022/01/04/gitlab-14-6-1-released/

Commit 8c7b82a2 authored by GARNIER Laurent's avatar GARNIER Laurent
Browse files

Revert "Resolve "script prepare.sh""

mistake...
This reverts commit 42c9bd8a.
parent a722fc7f
Pipeline #124030 passed with stages
in 5 minutes
...@@ -94,7 +94,7 @@ For convenience, all containers not running as root (django, mysql, registry) ...@@ -94,7 +94,7 @@ For convenience, all containers not running as root (django, mysql, registry)
have their user overridden to the UID:GID of the developer running have their user overridden to the UID:GID of the developer running
docker-compose. This is managed with the `DOCKERUSER` environment variable set docker-compose. This is managed with the `DOCKERUSER` environment variable set
[in the `.env` file](https://docs.docker.com/compose/environment-variables/#the-env-file) by [in the `.env` file](https://docs.docker.com/compose/environment-variables/#the-env-file) by
`bootstrap` script. `prepare.sh`.
For convenience (again), there is an extra external volume for `dev-django`, For convenience (again), there is an extra external volume for `dev-django`,
`dev-controller` and `dev-ssh` so that the source directory of the app is mounted `dev-controller` and `dev-ssh` so that the source directory of the app is mounted
...@@ -243,23 +243,23 @@ Re-open your session (to be effectively in the docker group) ...@@ -243,23 +243,23 @@ Re-open your session (to be effectively in the docker group)
#### **dev-mysql** initialisation fails #### **dev-mysql** initialisation fails
At [Getting started](#getting-started) step 2 you should have create the The `prepare.sh` script (also sourced by the `./bootstrap` script) creates the
`/data/dev/*/` with the ownership set to the calling user. Otherwise it will be owned by root and you may have errors like: `/data/dev/*/` with the ownership set to the calling user. **Be sure not to run
it as root**, otherwise it will be owned by root and you may have errors like:
mkdir: cannot create directory ‘/vol/rw’: Permission denied mkdir: cannot create directory ‘/vol/rw’: Permission denied
mkdir: cannot create directory ‘/vol/log’: Permission denied mkdir: cannot create directory ‘/vol/log’: Permission denied
If somehow you skipped this step, you can reset the ownership to the current user: If somehow you skipped this step, you can reset the ownership to the current user:
sudo chown $USER: /data/dev sudo chown $USER: /data/dev
sudo chown -R $USER: /data/dev/{registry,mysql,django} sudo chown -R $USER: /data/dev/{registry,mysql,django}
If you are completely lost, you can just restart the initialisation from scratch: If you are completely lost, you can just restart the initialisation from scratch:
fig down fig down
sudo rm -rf /data/dev sudo rm -rf /data/dev
sudo mkdir -p /data/dev . prepare.sh
sudo chown $USER: /data/dev
./bootstrap ./bootstrap
...@@ -318,7 +318,7 @@ TODO ? ...@@ -318,7 +318,7 @@ TODO ?
supervisorctl stop rails supervisorctl stop rails
rails server rails server
</pre> </pre>
) )
## ssh ## ssh
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment