stump: 404 after docker compose up

Describe the bug After docker compose (Raspberry Pi 5) app seems to be working but not able to access it only getting 404 No logs of any kind.

To Reproduce

dsavic@rpi5:~/stump $ docker compose logs -f WARN[0000] /home/dsavic/stump/docker-compose.yaml: version is obsolete stump | Adding group stump with gid 1000 stump | Adding group stump' (GID 1000) ... stump | Done. stump | Adding user stump with uid 1000 stump | Adding system user stump’ (UID 1000) … stump | Adding new user stump' (UID 1000) with group stump’ … stump | Not creating home directory `/home/stump’.

docker compose :

version: ‘3.3’ services: stump: image: aaronleopold/stump:nightly container_name: stump # Replace my paths (prior to the colons) with your own volumes: - /home/dsavic/stump/stumpconf:/config - /home/dsavic:/data

ports:
  - 10801:10801
environment:
  - PUID=1000
  - PGID=1000
  # This `environment` field is optional, remove if you don't need it.
  # I am using it as an example here, but it's actually a default value.
  - STUMP_CONFIG_DIR=/config
  - STUMP_VERBOSITY = 3
restart: unless-stopped

Expected behavior access through local network.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: [e.g. macOS, Windows, Linux, iOS, watchOS, Android]

Smartphone (please complete the following information):

Device: [e.g. iPhone12, Samsung S10, etc.]
OS: [e.g. iOS15.4.1]

Additional context Add any other context about the problem here.

About this issue

Original URL
State: closed
Created 2 months ago
Comments: 18

Most upvoted comments

@adityatelange @dsavicIre Can you please verify the issue is resolved with the nightly tag which was built over night? A quick Look at the logs doesn’t show the previous issue occurred

I confirm, pages are now loading no more 404s on aaronleopold/stump:nightly@sha256:7395665ab0c2291adf70d67c4e1c7f2751322ca5572dbe1418870a762a97fdb4.

Thanks for resolving the issue quickly. Stump has got great potential, and good vision. - happy stump user 😃

adityatelange on Apr 25, 2024

Confirming as well , all good !

Thanks vm

dsavicIre on Apr 25, 2024

Awesome! 👏 Thanks for verifying!

Once I fix the latest and 0.0.2 tags I’ll close this issue out

aaronleopold on Apr 25, 2024

So I think I figured out what is going on here. It seems like it’s related to https://github.com/nodejs/docker-node/issues/1335, and I realized this once I noticed the following:

The web bundle is missing in the image! The docker build is swallowing errors during the web build step, which is how it slipped through, e.g. see the latest nightly build: https://github.com/stumpapp/stump/actions/runs/8792186339/job/24127849892#step:4:5742

The first instance where this started, after pouring through the log history of the actions, seems to be here, which lines up exactly with when the migration off of pnpm landed in develop which triggers an amd64+arm64 build (experimental is amd64 only)

It seems like it only affects arm64, which also explains why I couldn’t replicate the issue right away since I did most of my testing ssh’d into my server.

I’m curious how/if this issue would persist if I were to swap back to my self-hosted runner, since it is less resource constrained and might not experience the network issues. I’m not overly fond of one of the resolutions in that linked issue being to just bump the timeout, and others involve downgrading node. Regardless, I’ll add some protections to the Dockerfile as to not swallow and miss the error.

I’ll try to have this fully resolved by the weekend with a rebuilt 0.0.2 arm build, time permitting.

aaronleopold on Apr 24, 2024

Same with v0.0.2 release. https://hub.docker.com/layers/aaronleopold/stump/0.0.2/images/sha256-75d9060c73092b38561c924280298bc1c841bcf1a7f8ef32bef4824326249651?context=explore

Are you running on arm, as well?

aaronleopold on Apr 24, 2024