public folder missing content when running in Kubernetes #71

Closed
opened 2026-02-04 16:59:37 +03:00 by OVERLORD · 1 comment
Owner

Originally created by @teq0 on GitHub (Feb 25, 2021).

I'm trying to get Planka running in my Kubernetes cluster (Raspberry Pi, K3s, arm64) and although connectivity all seems to be OK none of the static files, like manifest.json or any js files are being returned, they all get a 404.

I exec'd into the container, and the public folder only has the folders attachments, project-background-images and user-avatars, all of which are empty.

Comparing to a working Docker version I can see that the public folder should have all the static content in it as well.

Does the public folder get populated after the container starts? Or is the static content missing from the arm64 version of the container maybe?

Originally created by @teq0 on GitHub (Feb 25, 2021). I'm trying to get Planka running in my Kubernetes cluster (Raspberry Pi, K3s, arm64) and although connectivity all seems to be OK none of the static files, like manifest.json or any js files are being returned, they all get a 404. I exec'd into the container, and the public folder only has the folders attachments, project-background-images and user-avatars, all of which are empty. Comparing to a working Docker version I can see that the public folder should have all the static content in it as well. Does the public folder get populated after the container starts? Or is the static content missing from the arm64 version of the container maybe?
Author
Owner

@teq0 commented on GitHub (Feb 25, 2021):

Never mind, user error, I had a problem with how I mapped the volumes.

@teq0 commented on GitHub (Feb 25, 2021): Never mind, user error, I had a problem with how I mapped the volumes.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/planka#71