issue when doing docker compose up #3514

Existing issue

• I searched the existing issues and could not find a matching report.

Product variant

Self-hosted

Reactive Resume version

5.3.0

Area

Resume builder & data

Environment

cachyos

Summary

i had already successfully ran reactive resume before but had issue
this is my container before when i did docker ps -a
d92a724c5202 034cd2e3368f "docker-entrypoint.s…" 2 months ago Exited (137) 2 months ago reactive_resume-reactive_resume-1
e7256ae32970 quay.io/minio/mc:latest "/bin/sh -c '\n slee…" 2 months ago Exited (0) 2 months ago reactive_resume-seaweedfs_create_bucket-1
380986b9cc83 4aabea78cf39 "docker-entrypoint.s…" 2 months ago Exited (0) 2 months ago reactive_resume-postgres-1
bd4c72dbfa0f 2838d5524559 "docker-entrypoint.s…" 2 months ago Exited (0) 2 months ago reactive_resume-redis-1
5e93e0b23a84 f898c91e42d7 "/entrypoint.sh serv…" 2 months ago Exited (137) 2 months ago reactive_resume-seaweedfs-1

when doing docker compose up i encounter the below issue. it has already downloaded .note i already previously have got it to run but now it failed

[+] up 41/41
✔ Image chrislusf/seaweedfs:latest Pulled 77.4s
✔ Image quay.io/minio/mc:latest Pulled 35.9s
✔ Image redis:latest Pulled 51.8s
✔ Image postgres:latest Pulled 85.5s
[+] Building 2.9s (4/4) FINISHED
=> [internal] load local bake definitions 0.0s
=> => reading from stdin 616B 0.0s
[+] up 41/42l] load build definition from Dockerfile 0.0s
✔ Image chrislusf/seaweedfs:latest Pulled 77.4s
✔ Image quay.io/minio/mc:latest Pulled 35.9s
✔ Image redis:latest Pulled 51.8s
✔ Image postgres:latest Pulled 85.5s
⠙ Image reactive_resume-reactive_resume Building 2.9s
WARNING: current commit information was not captured by the build: failed to read current commit information with git rev-parse --is-inside-work-tree

Dockerfile:1

1 | >>> # syntax=docker/dockerfile:1.7

2 |

3 | ARG NODE_VERSION=24

failed to solve: failed to prepare sha256:327211ea034026032264266ca671642dba140d0d42af811bcc58a245c42b579b as olni1gscwfglogyjkkv4s56l6: parent snapshot sha256:327211ea034026032264266ca671642dba140d0d42af811bcc58a245c42b579b does not exist: not found

Steps to reproduce

docker compose up

Expected behavior

container should start without error

Actual behavior

error
[+] up 41/41
✔ Image chrislusf/seaweedfs:latest Pulled 77.4s
✔ Image quay.io/minio/mc:latest Pulled 35.9s
✔ Image redis:latest Pulled 51.8s
✔ Image postgres:latest Pulled 85.5s
[+] Building 2.9s (4/4) FINISHED
=> [internal] load local bake definitions 0.0s
=> => reading from stdin 616B 0.0s
[+] up 41/42l] load build definition from Dockerfile 0.0s
✔ Image chrislusf/seaweedfs:latest Pulled 77.4s
✔ Image quay.io/minio/mc:latest Pulled 35.9s
✔ Image redis:latest Pulled 51.8s
✔ Image postgres:latest Pulled 85.5s
⠙ Image reactive_resume-reactive_resume Building 2.9s
WARNING: current commit information was not captured by the build: failed to read current commit information with git rev-parse --is-inside-work-tree

Dockerfile:1

1 | >>> # syntax=docker/dockerfile:1.7

2 |

3 | ARG NODE_VERSION=24

failed to solve: failed to prepare sha256:327211ea034026032264266ca671642dba140d0d42af811bcc58a245c42b579b as olni1gscwfglogyjkkv4s56l6: parent snapshot sha256:327211ea034026032264266ca671642dba140d0d42af811bcc58a245c42b579b does not exist: not found

Template

None

Logs and screenshots

No response