Upgrade from 1.3.11 to 1.4.3 fails #65
Comments
|
Support for the PGID and PUID environment variables was actually just added with the release of 1.4.2. I guess that these variables had no effect before 1.4.2 and are now causing problems, because it tries to create a group with id 100. The issue is that this id is actually in use by the I'll try to fix this for the next release by checking if the id's are in use before trying to create the user and group. |
|
For those not that versed in the internals, could you write a comment please on how to actually achieve this upgrade? I'm trying to get from 1.2.7 to 1.4.4 and it fails for the same reason I suppose. I'm well versed in Linux, but not the internals of UNMS. |
|
I have since found the command line upgrade instruction: It would be really great if the GUI would actually inform the user that's doing the upgrade about this :-o Especially since the GUI upgrade it the official way. |
|
Hello @lifeboy, I'm not sure if you are using this docker container image? This repository is not for the official UISP, but rather for a 3rd party docker image for running UISP in a single container. If you are using this image and therefore not the official way of installing UISP, you will need to stop the UISP container, remove it, pull the new image and then create a new container (make sure to use the same /config path as before), which may look like this: However, if you are using the official way of installing UISP, which you seem to be doing, you will need to upgrade to 1.3.X first before upgrading to 1.4.X, because the upgrade script no longer allows you to skip major versions, but only minor versions.
after upgrading to 1.3.X, you should be able to upgrade to 1.4.X using the GUI (or by executing the command you posted). |
@skjnldsv Hello, please can you share your Traefik config for UISP, I have a problem to setup wss, thanks. |
traefikversion: "3.7"
services:
proxy:
# The official v2 Traefik docker image
image: traefik:v2.8
ports:
# Bind to host, advanced syntax to get real IPs
- target: 80
published: 80
mode: host
- target: 443
published: 443
mode: host
- target: 9000
published: 9000
mode: host
command:
# Enables the web UI and tells Traefik to listen to docker
- --api=true
- --api.dashboard=true
# Features
- --accesslog=true
# Debug mode
# - --api.debug=true
# - --log.level=DEBUG
# Define providers
- --providers.docker=true
- --providers.docker.swarmMode=true
- --providers.docker.exposedbydefault=false
- --providers.docker.network=proxy
- --providers.file.directory=/etc/traefik/conf.d
- --providers.file.watch=true
# Allow internal self signed cert
- --serversTransport.insecureSkipVerify=true
# Define default ports
- --entrypoints.web.address=:80
- --entrypoints.websecure.address=:443
- --entrypoints.websocket.address=:9000
# Register letsencrypt resolver
- --certificatesResolvers.letsencryptresolver.acme.tlsChallenge=true
- --certificatesresolvers.letsencryptresolver.acme.email=skjnldsv@xxxxxxxx.xx
- --certificatesResolvers.letsencryptresolver.acme.storage=/letsencrypt/acme.json
...
docker-unmsversion: "3.7"
services:
app:
image: nico640/docker-unms:latest
networks:
- proxy
ports:
# Web ui + Websocket
- 443
# Netflow
- 2055:2055/udp
environment:
- TZ=Europe/Paris
volumes:
- /mnt/docker/volumes/unms:/config
deploy:
mode: replicated
replicas: 1
placement:
constraints:
- node.role == worker
restart_policy:
condition: on-failure
delay: 5s
max_attempts: 3
window: 120s
resources:
limits:
cpus: '1'
memory: 1024M
reservations:
cpus: '0.25'
memory: 256M
labels:
traefik.enable: "true"
traefik.http.routers.unms.rule: Host(`xxxx.xxxxxx.com`)
traefik.http.routers.unms.entrypoints: websecure
traefik.http.routers.unms.tls.certresolver: letsencryptresolver
traefik.http.routers.unms.service: unms
# fake value https://github.com/containous/traefik/issues/5732
traefik.http.services.unms.loadbalancer.server.port: 443
traefik.http.services.unms.loadbalancer.server.scheme: https
networks:
proxy:
external: true |
Hi, I haven't updated the image in a while, and it recently started to fail.
I haven't changed my config in like a year. 1.3.11 works fine
I see multiple worrying issues in the log after:
addgroup: gid '100' in useandadduser: unknown group unmsThen I think lots of those issues comes down to the unms user not existing ? 🤔
Config
The text was updated successfully, but these errors were encountered: