You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I destroyed my Postgres database because I did not define an HTTP connect proxy for the database. The update script from Postgres 10 to 12 uses apt. But apt needs my proxy to get out. After docker-compose down and up -d, GitLab booted up, but all users and repos were gone!
The recovery steps were approximate:
# Shut down and delete four containers and the network:
docker-compose down
mkdir ./kaputt-2020-05-30/
mv ./volume_gitlab/data/ ./kaputt-2020-05-30/
mv ./volume_postgresql/ ./kaputt-2020-05-30/
mv ./volume_redis/ ./kaputt-2020-05-30/
# Change the docker-compose.yml file to the versions of the last backup: sameersbn/postgresl:10-2 and sameersbn/gitlab:12.9.5 !
docker-compose up -d
# Put the last backup as the only backup:
cp ./kaputt-2020-05-30/data/backups/1590793353_2020_05_29_12.9.5_gitlab_backup.tar ./volume_gitlab/data/backups/
docker-compose exec gitlab bash
su - git
export PGUSER=gitlab
export PGPASSWORD=***
cd gitlab
# Restore the backup:
bundle exec rake gitlab:backup:restore RAILS_ENV=production
!!! Define your HTTP connect proxy in /etc/apt/apt.conf and mount it in docker-compose.yml file under volumes !!!
I destroyed my Postgres database because I did not define an HTTP connect proxy for the database. The update script from Postgres 10 to 12 uses apt. But apt needs my proxy to get out. After docker-compose down and up -d, GitLab booted up, but all users and repos were gone!
The recovery steps were approximate:
!!! Define your HTTP connect proxy in /etc/apt/apt.conf and mount it in docker-compose.yml file under volumes !!!
Now you can change versions in Postgres image and GitLab image - one after the other. Works.
docker-compose logs -f
Please help for the last step.
The text was updated successfully, but these errors were encountered: