Trying to run the 8.3.0 upgrade script

PeerTube
1

Good day.

I am new to posting here and have only been running Peertube for about 3 months. Most of what I have encountered has been fairly straightforward.

I am running Peertube 8.3.0 on Docker (using Dockhand and Docker Compose) behind a reverse proxy. I upgraded to the latest 8.3.0 image yesterday and I am trying to run the upgrade script after the « Migrations finished. New migration version schema: 1125 » message detailed in the release notes here: Changelog | PeerTube documentation

I am trying to run the script based on the instructions below:

  • Docker installation: cd /var/www/peertube-docker && docker compose exec -u peertube peertube node dist/scripts/migrations/peertube-8.3.js

I am using docker compose, but the /var/www/peertube-docker directory doesn’t exist on my local host. I can, however find the peertube-8.3.js file in /app/dist/scripts/migrations/peertube-8.3.js on my docker container. I am assuming that I need to replace the « /var/www » and the « node dist/scripts » with paths that are appropriate for my installation. Question: how can I find what I need to run the upgrade script?

root@bigstorage:/usr/local# sudo docker compose ls | grep peertube
peertube            restarting(1), running(3)   /app/data/stacks/Production/peertube/docker-compose.yml
peertuberunnergpu   running(1)                  /app/data/stacks/Production/peertuberunnergpu/docker-compose.yml

Thanks in advance.

2

Since you have PeerTube installed in /app/data/stacks/Production/peertube, the command should be:

cd /app/data/stacks/Production/peertube && docker compose exec -u peertube peertube node dist/scripts/migrations/peertube-8.3.js
3

Thank you for that answer and explaining how I should approach it. I think I figured it out, as a result.

There is no /app/data/stacks… folder. « Dockhand », the Portainer replacement stores all of the docker-compose.yml files in its own container in an /app/data/stacks/Production/ folder. Fortunately that /app/data/stacks/Production folder is mapped to « /var/lib/docker/volumes/dockhand_data/_data/stacks/Production » on the local host. In the end, I ran this command with your very helpful information and I got this output:

root@bigstorage:/var/lib/docker/volumes/dockhand_data/_data/stacks/Production/peertube# cd /var/lib/docker/volumes/dockhand_data/_data/stacks/Production/peertube && sudo docker compose exec -u peertube peertube node dist/scripts/migrations/peertube-8.3.js
Filling videoSearch table with existing videos...
videoSearch table filled.

Migrating video infohashes...
Video infohashes migrated.

I ran it again, just to make sure it was okay and I got:

root@bigstorage:/var/lib/docker/volumes/dockhand_data/_data/stacks/Production/peertube# cd /var/lib/docker/volumes/dockhand_data/_data/stacks/Production/peertube && sudo docker compose exec -u peertube peertube node dist/scripts/migrations/peertube-8.3.js
Filling videoSearch table with existing videos...
videoSearch table filled.

Video infohashes already migrated, skipping.

Does that look good? If yes, then thank you very much!

4

Yup, that’s right.