[GH-ISSUE #881] Version number of pangolin docker not updated #29508

New Issue

GiteaMirror · 2026-06-13T09:22:31-05:00

GiteaMirror commented

2026-06-13 09:22:31 -05:00

Originally created by @S-North on GitHub (Jun 10, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/881

I've just updated the docker image to the latest with a docker compose pull, which executed without error. I checked it was trying to pull latest.

name: pangolin
services:
  pangolin:
    image: fosrl/pangolin:latest
    container_name: pangolin

The version in the pangolin dashboard before the pull was 1.4.0. After the pull the pangolin version does not appear to have updated, it still says 1.4.0 instead of the latest 1.5.1.

I'm not sure if the version of pangolin was not updated, or just the text in the UI that is wrong. I was not able to run docker compose exec pangolin bash to try and verify Pangolin's version.

There was this in the logs though in case it is relevent;

npm error path /app
npm error command failed
npm error signal SIGTERM
npm error command sh -c NODE_OPTIONS=--enable-source-maps NODE_ENV=development ENVIRONMENT=prod sh -c 'node dist/migrations.mjs && node dist/server.mjs'
npm error A complete log of this run can be found in: /root/.npm/_logs/2025-06-10T06_21_42_611Z-debug-0.log

> @fosrl/pangolin@0.0.0 start
> NODE_OPTIONS=--enable-source-maps NODE_ENV=development ENVIRONMENT=prod sh -c 'node dist/migrations.mjs && node dist/server.mjs'

Originally created by @S-North on GitHub (Jun 10, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/881 I've just updated the docker image to the latest with a `docker compose pull`, which executed without error. I checked it was trying to pull latest. ``` name: pangolin services: pangolin: image: fosrl/pangolin:latest container_name: pangolin ``` The version in the pangolin dashboard before the pull was 1.4.0. After the pull the pangolin version does not appear to have updated, it still says 1.4.0 instead of the latest 1.5.1. ![Image](https://github.com/user-attachments/assets/731a4682-d38a-4570-ad81-aa9446387e85) I'm not sure if the version of pangolin was not updated, or just the text in the UI that is wrong. I was not able to run `docker compose exec pangolin bash` to try and verify Pangolin's version. There was this in the logs though in case it is relevent; ``` npm error path /app npm error command failed npm error signal SIGTERM npm error command sh -c NODE_OPTIONS=--enable-source-maps NODE_ENV=development ENVIRONMENT=prod sh -c 'node dist/migrations.mjs && node dist/server.mjs' npm error A complete log of this run can be found in: /root/.npm/_logs/2025-06-10T06_21_42_611Z-debug-0.log > @fosrl/pangolin@0.0.0 start > NODE_OPTIONS=--enable-source-maps NODE_ENV=development ENVIRONMENT=prod sh -c 'node dist/migrations.mjs && node dist/server.mjs' ```

GiteaMirror added the stale label 2026-06-13 09:22:31 -05:00

GiteaMirror closed this issue

2026-06-13 09:22:32 -05:00

GiteaMirror commented

2026-06-13 09:22:32 -05:00

@Momi-V commented on GitHub (Jun 10, 2025):

You need to reapply the compose stack after pulling.

docker compose pull
docker compose down
docker compose up -d

@Momi-V commented on GitHub (Jun 10, 2025): You need to reapply the compose stack after pulling. ``` docker compose pull docker compose down docker compose up -d ```

GiteaMirror commented

2026-06-13 09:22:32 -05:00

@S-North commented on GitHub (Jun 10, 2025):

Sorry, I should have said I did do a docker compose restart before.
However the explicit down then up -d did actually fix the problem. I didn't realise there was a difference between restart & up/down.
Thanks for the help, I am on 1.5.1 now.

@S-North commented on GitHub (Jun 10, 2025): Sorry, I should have said I did do a `docker compose restart` before. However the explicit `down` then `up -d` did actually fix the problem. I didn't realise there was a difference between restart & up/down. Thanks for the help, I am on 1.5.1 now.

GiteaMirror commented

2026-06-13 09:22:33 -05:00

@Momi-V commented on GitHub (Jun 10, 2025):

Then I think you can close this issue.

down + up is already the way it's done in the documentation, this is expected behavior for any docker compose stack and nothing the Pangolin devs could change.

@Momi-V commented on GitHub (Jun 10, 2025): Then I think you can close this issue. `down + up` is already the way it's done in the documentation, this is expected behavior for any docker compose stack and nothing the Pangolin devs could change.

GiteaMirror commented

2026-06-13 09:22:33 -05:00

@github-actions[bot] commented on GitHub (Jun 25, 2025):

This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.

@github-actions[bot] commented on GitHub (Jun 25, 2025): This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.

Sign in to join this conversation.

Branches Tags

main

local-connection

crowdin_dev

dev

dependabot/npm_and_yarn/npm-dependencies-338850a190

dependabot/go_modules/install/go-install-dependencies-3804ca7238

dependabot/docker/docker-dependencies-4faa477378

dependabot/github_actions/github-actions-dependencies-6d79802a48

api-improvements

feat/remember-last-idp-on-smart-login-form

refactor/batch-status-requests

dependabot/npm_and_yarn/multi-5f1280885e

fix/non-semver-version-error

private-resource-page

resource-launcher

backhaul

exit-node-reconnect

feat/command-palette

ssh

delete-account

msg-delivery

org-only-idp

cicd

patch

site-targets-auto-login

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/pangolin#29508