Why is postiz docker image so large? #830
Replies: 5 comments 2 replies
-
|
It’s a monorepo so it’s a bit big, we will try to find ways to decrease the
image size
…On Fri, Jun 20, 2025 at 1:41 PM Neelesh Kumar ***@***.***> wrote:
image.png (view on web)
<https://github.com/user-attachments/assets/7178f5e7-ff3b-41b9-9bd6-05e72766043a>
Ideally should be less than 1GB, it's 4.3 GB
—
Reply to this email directly, view it on GitHub
<#830>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AX32VBVV4UWOKS56A2JI6X33EOUIPAVCNFSM6AAAAAB7XP4JBOVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZYGQ3TIOJWGA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Consider breaking the image into multiple images like frontend, backend, upload service etc |
Beta Was this translation helpful? Give feedback.
-
|
Caddy should be optional as I'm using nginx with certbot. Solutions like cloudflare tunnels make even reverse proxy and certbot unnecessary. |
Beta Was this translation helpful? Give feedback.
-
|
There is one package.json, so it is not optional, we might try to use something
like webpack to create one compiled file with the dependencies
…On Fri, Jun 20, 2025 at 1:43 PM Neelesh Kumar ***@***.***> wrote:
Consider breaking the image into multiple images like frontend, backend,
scheduler service (if you have one) etc
—
Reply to this email directly, view it on GitHub
<#830 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AX32VBWYF2LH7UIESCI6BBT3EOUS3AVCNFSM6AAAAAB7XP4JBOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNJSG4YDCNY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
node modules alone is 2.7GB. No wonder the docker image is 4.3GB |
Beta Was this translation helpful? Give feedback.
-
|
The docker image created in this project contains all the node modules. However, all the node modules are not needed for production run. The node modules can be removed by using a multi stage Docker build. This will reduce the size of the image by more than half. Please take a look https://chat.anyllm.in/share/K3sBuF-agfH14xl-v9w6M |
Beta Was this translation helpful? Give feedback.
-
|
@nevo-david I wrote an optimized Dockerfile and was able to reduce the image size from 5.1GB to 2.2GB. Upon further inspection, I noticed that there were a few packages in prod dependencies that should be in devDependencies. Can you take a look at these and update package.json? Unnecessary Modules in Production (Can be removed): Build Tools & Compilers (~50MB):
Testing Tools (~35MB):
Duplicate/Unnecessary Binaries (~110MB):
Bloated Dependencies that could be optimized:
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Ideally should be less than 1GB, it's 4.3 GB.
Consider breaking the image into multiple images like frontend, backend, scheduler service (if you have one) etc
Beta Was this translation helpful? Give feedback.
All reactions