You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Docker image shouldn't behave differently on Kubernetes, so this must have something to do with your deployment configuration. Looking at the deployment.yaml file, it seems like you're mounting the whole /directus folder instead of /directus/uploads (see https://docs.directus.io/guides/installation/docker/#persistence).
Preflight Checklist
Describe the Bug
Installing Directus via its Dockerhub container image on a Kubernetes cluster will cause the image to not have its package.json.
There are no traces of the Dockerfile's builder steps, which indicate that these might be getting skipped over. There is also no
node_modules
folder.The absence of
package.json
andnode_modules
leads to extensions being unable to be loaded.To Reproduce
I used a basic setup with a custom helm chart, however, this is likely also reproducible in other chart setups.
/directus
and runls
.package.json
andnode_modules
.What version of Directus are you using?
9.0.0-rc.95
What version of Node.js are you using?
16.9.1
What database are you using?
Postgres 12.8
What browser are you using?
(irrelevant)
What operating system are you using?
Linux (Directus' Dockerfile)
How are you deploying Directus?
Kubernetes
The text was updated successfully, but these errors were encountered: