Hmm this is bizarre — I’ve tested it locally (with podman on macOS), and it started normally.
I’ll need to try to recreate your environment. What host OS is this, and what container management? Docker on Linux?
And to confirm, you have tried deleting the old image and docker pull <new one>
Also please verify
docker images --digests saspus/duplicacy-web:v1.8.3
Returns
sha256:0b58d6e0af4138dd15b1a98b39564730bed5e1afc99aa4568af3e940fc532571
Just tried on a raspberry pi — works fine
pi@raspberry:~ $ podman run docker.io/saspus/duplicacy-web:v1.8.3
Trying to pull docker.io/saspus/duplicacy-web:v1.8.3...
Getting image source signatures
Copying blob 6b59a28fa201 done
Copying blob 621a81ace40a done
Copying blob bf713d46881b done
Copying config 26042e0fc4 done
Writing manifest to image destination
Storing signatures
launch.sh runing as user root:root(0:0)
Using machine-id = df878babffb6779cc147f85f68fba7fe
duplicacy_web runing as user root:root(0:0)
Logging tail of the log from this moment on
Starting duplicacy
Log directory set to /logs
Duplicacy Web Edition 1.8.3 (5A554A)
Starting the web server at http://[::]:3875