I also just bumped in to this issue when updating from the UI, however using: curl -L install.fermentrack.com | bash
still required me to use this before it would work: sudo apt-get update --allow-releaseinfo-change
I also got an error on the redis install, which I assume is because redis is already running?
*** ERROR: Port 6379 is required by Redis, but is currently in use. Installation cannot continue.
Seems the script doesn't stop the docker containers when it tries to run the update, so it was erroring. I manually stopped all containers and it allowed me to run the script: docker stop $(docker ps -a -q)
Also as the script progresses after stopping the docker containers to allow it to install, it then seems to get stuck on:
Waiting for PostgreSQL to become available...
It could just be me being impatient but it's perhaps been doing that for at least 10 minutes
Looking at docker it seems* to be running but I'm not sure what the readiness probe is testing for:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
3f4fcee59ed2 jdbeeler/fermentrack:latest "/entrypoint python …" 16 minutes ago Up 16 minutes fermentrack-tools_django_run_1
4f638f73035b fermentrack_postgres "docker-entrypoint.s…" 16 minutes ago Up 16 minutes fermentrack-tools_postgres_1
61f35551caac fermentrack_redis "docker-entrypoint.s…" 16 minutes ago Up 16 minutes fermentrack-tools_redis_1
Exec'ing in I can see postgrsql is running:
[email protected]:~ $ docker exec fermentrack-tools_postgres_1 pg_isready
/var/run/postgresql:5432 - accepting connections
I updated the os with apt-get update, did a reboot and then re-ran the install script, it seems to get further now but I get this error:
::: Waiting for Fermentrack install to initialize and become responsive.
::: Fermentrack may take up to 3 minutes to first boot as the database is being initialized.
..........................................................................................missing.
*** ERROR: Unable to find an initialized, responsive instance of Fermentrack
Weirdly the application seems to be running despite the error :s