Trap notice: your Silverbullet instance might not be updating

General
1

Hi,

This is my finding today about several issues I had previously. I am pretty confused that why some of the fixes on the latest commit cannot solve the problem on my instance.

Turns out that if you were using docker-compose and you were using the build syntax that we were recommending previously (shown below), then pulling the latest silverbullet image and then run docker compose up -d won’t update your instance.

services:
   silverbullet:
    build:
      context: .
      dockerfile_inline: |
        FROM ghcr.io/silverbulletmd/silverbullet:v2
        RUN apk add pandoc
    container_name: silverbullet

In the hindsight it is quiet reasonable: since the silverbullet:v2 is contained in the string. So when you were using this syntax and you want to update your silverbullet instance inside the docker compose. You should use docker compose up -d --build.

Just a notice for other people so that you were not as confused as I was in the past months.

5 Likes