Upgrade from 0.29.0 to 0.31.1 crashed my Stirling-PDF

[bpNetwork]

Hello,
i use Proxmox, Docker and Portainer with Ubuntu-Server.
After each upgrade from Stirling-PDF from 0.29.0 to 0.31.1 my Stirling-PDF stop running. Portainer shows me this message:
"exited - code 1"

I am a newbie with linux and docker.

Am I causing the error or the upgrade? I have a backup of my 0.29.0 version and can downgrade again at any time. Should I wait for another newer version of Stirling-PDF and only then upgrade?

### The logs:

Copying original files without overwriting existing files
Running Stirling PDF with DOCKER_ENABLE_SECURITY=true and VERSION_TAG=0.31.1
Trying to download from: https://github.com/Stirling-Tools/Stirling-PDF/releases/download/v0.31.1/Stirling-PDF-with-login.jar
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:02 --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:03 --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:04 --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:05 --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:06 --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:07 --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:08 --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:09 --:--:--     0curl: (6) Could not resolve host: github.com
Trying to download from: https://github.com/Stirling-Tools/Stirling-PDF/releases/download/0.31.1/Stirling-PDF-with-login.jar
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0
100     9  100     9    0     0      4      0  0:00:02  0:00:02 --:--:--     4
Installing font package: font-noto
fetch https://dl-cdn.alpinelinux.org/alpine/v3.20/main/x86_64/APKINDEX.tar.gz
fetch https://dl-cdn.alpinelinux.org/alpine/v3.20/community/x86_64/APKINDEX.tar.gz
fetch https://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/APKINDEX.tar.gz
fetch https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz
fetch https://dl-cdn.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz
(1/4) Installing font-noto-common (23.7.1-r0)
(2/4) Installing font-noto-math (23.7.1-r0)
(3/4) Installing font-noto-symbols (23.7.1-r0)
(4/4) Installing font-noto (23.7.1-r0)
Executing fontconfig-2.15.0-r1.trigger
Executing mkfontscale-1.2.2-r6.trigger
OK: 1268 MiB in 422 packages
Setting permissions and ownership for necessary directories...
Error: Invalid or corrupt jarfile /app.jar

[dosubot[bot]]

Hey there, @bpNetwork! I'm here to help you with any bugs, questions, or contributions you have regarding Stirling-PDF. Let's squash those bugs together! 🤖

The error message "Could not resolve host: github.com" indicates a DNS resolution issue, which is preventing the download of the necessary JAR file. This is likely causing the "Invalid or corrupt jarfile" error because the file isn't being downloaded correctly.

Here are some steps you can take to resolve this issue:

1. Check Network Configuration: Ensure that your server has internet access and can resolve DNS queries. You can test this by running ping github.com or nslookup github.com from your server.

2. DNS Settings: If DNS resolution is failing, you might need to configure your DNS settings. You can try using a public DNS server like Google's (8.8.8.8) or Cloudflare's (1.1.1.1).

3. Docker Network Configuration: Ensure that your Docker containers have access to the internet. You can check the network settings in Docker and ensure that the containers are using the correct network mode.

4. Retry the Upgrade: Once the DNS issue is resolved, try upgrading again. Make sure to pull the latest Docker image before starting the container.

5. Check for Proxy Settings: If your network uses a proxy, ensure that Docker is configured to use it. You can set proxy settings in Docker by configuring the Docker daemon.

If these steps don't resolve the issue, you might consider downgrading to version 0.29.0 temporarily and waiting for a newer version if the problem persists.

To continue talking to Dosu, mention @dosu.

[bpNetwork]

Hello,

Check Network Configuration: Ensure that your server has internet access and can resolve DNS queries. You can test this by running ping github.com or nslookup github.com from your server.

addi@Stirling-PDF:$ sudo ping github.com
[sudo] password for addi:
PING github.com (140.82.121.4) 56(84) bytes of data.
64 bytes from lb-140-82-121-4-fra.github.com (140.82.121.4): icmp_seq=1 ttl=52 time=18.1 ms
64 bytes from lb-140-82-121-4-fra.github.com (140.82.121.4): icmp_seq=2 ttl=52 time=16.9 ms
64 bytes from lb-140-82-121-4-fra.github.com (140.82.121.4): icmp_seq=3 ttl=52 time=20.3 ms
64 bytes from lb-140-82-121-4-fra.github.com (140.82.121.4): icmp_seq=4 ttl=52 time=17.0 ms
64 bytes from lb-140-82-121-4-fra.github.com (140.82.121.4): icmp_seq=5 ttl=52 time=17.0 ms
64 bytes from lb-140-82-121-4-fra.github.com (140.82.121.4): icmp_seq=6 ttl=52 time=16.8 ms
64 bytes from lb-140-82-121-4-fra.github.com (140.82.121.4): icmp_seq=7 ttl=52 time=17.5 ms
64 bytes from lb-140-82-121-4-fra.github.com (140.82.121.4): icmp_seq=8 ttl=52 time=17.0 ms
64 bytes from lb-140-82-121-4-fra.github.com (140.82.121.4): icmp_seq=9 ttl=52 time=16.8 ms
64 bytes from lb-140-82-121-4-fra.github.com (140.82.121.4): icmp_seq=10 ttl=52 time=17.4 ms
64 bytes from lb-140-82-121-4-fra.github.com (140.82.121.4): icmp_seq=11 ttl=52 time=16.7 ms
64 bytes from lb-140-82-121-4-fra.github.com (140.82.121.4): icmp_seq=12 ttl=52 time=16.7 ms
64 bytes from lb-140-82-121-4-fra.github.com (140.82.121.4): icmp_seq=13 ttl=52 time=16.8 ms
64 bytes from lb-140-82-121-4-fra.github.com (140.82.121.4): icmp_seq=14 ttl=52 time=16.9 ms
64 bytes from lb-140-82-121-4-fra.github.com (140.82.121.4): icmp_seq=15 ttl=52 time=16.8 ms
64 bytes from lb-140-82-121-4-fra.github.com (140.82.121.4): icmp_seq=16 ttl=52 time=17.2 ms
64 bytes from lb-140-82-121-4-fra.github.com (140.82.121.4): icmp_seq=17 ttl=52 time=17.0 ms
^C
--- github.com ping statistics ---
17 packets transmitted, 17 received, 0% packet loss, time 16023ms
rtt min/avg/max/mdev = 16.672/17.235/20.326/0.843 ms
addi@Stirling-PDF:$ sudo nslookup github.com
Server: 192.168.179.1
Address: 192.168.179.1#53

Non-authoritative answer:
Name: github.com
Address: 140.82.121.3

addi@Stirling-PDF:$ ^C
addi@Stirling-PDF:$

This works fine.

I went into Portainer and downloaded the image from docker.io, this worked without any problems. However, when I try to roll out the container again, this error also appears:

Error: Invalid or corrupt jarfile /app.jar