@ -98,3 +98,86 @@ sudo service openproject restart
## Docker-based installation
For Docker-based installations, assuming you have a backup as per the procedure described in the [Backing up](../backing-up) guide, you simply need to restore files into the correct folders (when using the all-in-one container), or restore the docker volumes (when using the Compose file), then start OpenProject using the normal docker or docker-compose command.
### Restoring a dump
Let's assume you want to restore a database dump given in a file, say `openproject.sql`.
If you are using docker-compose this is what you do after you started everything for the first time using `docker-compose up -d`:
1. Stop the OpenProject container using `docker-compose stop web worker`.
2. Drop the existing, seeded database using `docker exec -it db_1 psql -U postgres -c 'drop database openproject;`
3. Recreate the database using `docker exec -it db_1 psql -U postgres -c 'create database openproject owner openproject;`
4. Copy the dump onto the container: `docker cp openproject.sql db_1:/`
5. Source the dump with psql on the container: `docker exec -it db_1 psql -U postgres` followed by `\i openproject.sql`
6. Delete the dump on the container: `docker exec -it db_1 rm openproject.sql`
7. Restart the web and worker processes: `docker-compose start web worker`
This assumes that the database container is called `db_1`. Find out the actual name on your host using `docker ps | postgres`.
#### All-in-one container
Given a SQL dump `openproject.sql` we can create a new OpenProject container using it with the following steps.
1. Create the pgdata folder to be mounted in the OpenProject container.
2. Initialize the database.
3. Restore the dump.
4. Start the OpenProject container mounting the pgdata folder.
1)
First we create the folder to be mounted by our OpenProject container.
While we're at we also create the assets folder which should be mounted too.
```
mkdir /var/lib/openproject/{pgdata,assets}
```
2)
Next we need to initialize the database.
```
docker run --rm -v /var/lib/openproject/pgdata:/var/openproject/pgdata -it openproject/community:10
```
As soon as you see `CREATE ROLE` and `Migrating to ToV710AggregatedMigrations (10000000000000)` or lots of `create_table` in the container's output
you can kill it by pressing Ctrl + C. This then initialized the database under `/var/lib/openproject/pgdata`.
3)
Now we can restore the database. For this we mount the initialized `pgdata` folder using the postgres docker container.
```
docker run --rm -d --name postgres -v /var/lib/openproject/pgdata:/var/lib/postgresql/data postgres:9.6
```
Once the container is ready you can copy your SQL dump onto it and start `psql`.
```
docker cp openproject.sql postgres:/
docker exec -it postgres psql -U postgres
```
In `psql` you then restore dump like this:
```
DROP DATABASE openproject;
CREATE DATABASE openproject OWNER openproject;
\c openproject
\i openproject.sql
```
Once this has finished you can quit `psql` (using `\q`) and the container (`exit`) and stop it using `docker stop postgres`.
Now you have to fix the permissions that were changed by the postgres container so OpenProject can use the files again.
```
chown -R 102 /var/lib/openproject/pgdata
```
Your `pgdata` directory is now ready to be mounted by your final OpenProject container.
4)
Start the container as described in the [installation section](../../installation/docker/#recommended-usage) mounting `/var/lib/openproject/pgdata`.
Markus Kahl
4 years ago