Upgrading Apps

Portaininer

ssh into docker1

  1. docker stop portaininer
  2. docker rm portainer
  3. docker pull portainer/portainer-ce:latest
  4. . start_portainer.sh

start_portainer.sh

docker run -d -p 8000:8000 -p 9000:9000 -p 9443:9443 --name=portainer --restart=always \
-v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce

NB This can be done without affecting containers, i.e. no customer impact if this is done during working hours.

Docker Compose - Simple Projects

Can be used on any (perhaps I should say most) docker-compose projects.

  • cd {{folder containing docker-compose.yml}}
  • docker compose pull
  • docker compose up -d

Possible run docker image prune -f afterwards to remove unused images, but this may remove used, but not currently running images. Originally it was required to do a docker-compose down, but the new docker compose style commands supports restarting with optional re-create container, with just docker compose up -d.

NB This method works for all docker-compose projects. Proven on uptime-kurma, dashy and hugo.

Uptime Kurma

This was my original approach, but now I use the generic Docker-Compose method.

Old Method

ssh into pi1

  1. cd docker/uptime-kurma
  2. docker-compose stop
  3. docker-compose rm
  4. docker pull louislam/uptime-kuma:1
  5. docker-compose up -d

The docker-compose rm command may not be required.

ProxMox

ssh into metal1

  1. apt update
  2. apt upgrade
  3. reboot if it tells you to (i.e. for kernel ugrade)

** CAUTION ** When I followed those instructions, portainer failed to start, which meant none of the docker images configured with portainer were running. I has to manually start portainer and then start each stack/ container.

Version Upgrade

I followed https://www.servethehome.com/proxmox-ve-8-0-is-out-upgrading-linux-and-more/

  • pve7to8 tool to ensure there are not any major blockers then:
  • sed -i ’s/bullseye/bookworm/g’ /etc/apt/sources.list
    • I also had to update /etc/apt/sources.list.d/*
  • apt update
  • apt dist-upgrade

Modoboa - on far1

Visit https://mail.bazicloud.co.uk/core/#info/ to see what needs upgrading.

cd /srv/modoboa
. env/bin/activate
env/bin/pip3 install modoboa=2.1.2
env/bin/pip3 install modoboa_contacts==0.9.3
env/bin/pip3 install modoboa_radicale==1.6.3
env/bin/pip3 install modoboa_postfix_autoreply==1.7.1
env/bin/pip3 install modoboa_webmail==1.7.1
cd /mnt/games/bigDev/modoboa-installer
sudo python3 run.py --upgrade bazicloud.co.uk
# need to answer some prompts - just accept the defaults
systemctl restart uwsgi
systemctl restart nginx

Seems that both uwsgi and nginx need restarting in that order.

Modoboa packages and version as of June 2023:

modoboa==2.1.2
modoboa_amavis==1.4.0
modoboa_contacts==0.9.3
modoboa_pdfcredentials==1.5.0
modoboa_postfix_autoreply==1.7.1
modoboa_radicale==1.6.3
modoboa_sievefilters==1.6.0
modoboa_webmail==1.7.1

Ollama

Just repeat the installation command, currently (Feb 2024):

curl https://ollama.ai/install.sh | sh

Version being served can be checked using:

$ curl -sL http://localhost:11434/api/version
{"version":"0.1.23"}