This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-02-08
Channels
- # aleph (5)
- # announcements (3)
- # aws-lambda (16)
- # babashka (17)
- # beginners (59)
- # calva (168)
- # clerk (4)
- # clj-kondo (62)
- # clojure (77)
- # clojure-belgium (4)
- # clojure-brasil (10)
- # clojure-ecuador (3)
- # clojure-europe (41)
- # clojure-losangeles (2)
- # clojure-nl (2)
- # clojure-norway (24)
- # clojure-uk (2)
- # clojurescript (44)
- # clr (21)
- # community-development (7)
- # conjure (1)
- # cursive (3)
- # datalevin (15)
- # datomic (1)
- # deps-new (12)
- # emacs (45)
- # events (1)
- # fulcro (8)
- # funcool (7)
- # graphql (5)
- # hugsql (15)
- # jobs (2)
- # matcher-combinators (17)
- # meander (14)
- # membrane (31)
- # pathom (28)
- # pedestal (6)
- # practicalli (6)
- # re-frame (12)
- # releases (1)
- # remote-jobs (1)
- # shadow-cljs (32)
- # tools-deps (8)
- # vim (16)
We're running into file size limits when loading an uberjar in Lambda. We're basically at a point where adding a new dependency puts us over the limit. According to the docs the limit is 250M but that doesn't match our uberjar size, which went from 100M to 114M. Yes it's big, but not as big as they say is allowed
Any idea on how to navigate this? It can't be that the jar is simply full right? :-)
I was hoping not having to make that jump but if all else fails that's definitely an option
Alas, size is total of all layers so adding layers doesn't help with the 250M limit
Yeah it's what you get when you unzip the jar
unzip -Zt uberjar.jar
Took me a long time to grok that du -sh doesn't show the right result
they are trying to encourage you to use container images with their asymmetrical limits
Yeah I'm letting go of my resistance to docker after 10 yrs
I thought I could wait this one out but I was wrong about that