groove/Part-DB-server
1
0
Fork 0
mirror of https://github.com/Part-DB/Part-DB-server.git synced 2026-04-16 11:29:36 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 8

Added more warnings about sudo -E to docker docs

Browse source 
Related to issue #1319
This commit is contained in:
Jan Böhmer 2026-03-30 20:03:25 +02:00
parent 991daf0ead
commit 52df554b29
2 changed files with 7 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

5
docs/installation/installation_docker.md
View file

@ -95,6 +95,11 @@ services:
docker-compose up -d docker-compose up -d
``` ```
{: .warning }
> If you run a root console inside the docker container, and wanna execute commands on the webserver behalf, be sure to use `sudo -E` command (with the `-E` flag) to preserve env variables from the current shell.
> Otherwise Part-DB console might use the wrong configuration to execute commands.
6. Create the initial database with 6. Create the initial database with
```bash ```bash

2
docs/upgrade/1_to_2.md
View file

@ -60,6 +60,8 @@ The `php bin/console partdb:backup` command can help you with this.
If you want to change them, you must migrate them to the settings interface as described below. If you want to change them, you must migrate them to the settings interface as described below.
### Docker installation ### Docker installation
**When running the console commands from inside a docker container's shell as root, be sure to use `sudo -E` to preserve the environment variables, so that they are correctly passed to the command.**
1. Make a backup of your existing Part-DB installation, including the database, data directories and the configuration files and the file where you configure the docker environment variables. 1. Make a backup of your existing Part-DB installation, including the database, data directories and the configuration files and the file where you configure the docker environment variables.
2. Stop the existing Part-DB container with `docker compose down` 2. Stop the existing Part-DB container with `docker compose down`
3. Ensure that your docker compose file uses the new latest images (either `latest` or `2` tag). 3. Ensure that your docker compose file uses the new latest images (either `latest` or `2` tag).