i see a bunch of cruft in what's supposed to be th...
# lucee
j
i see a bunch of cruft in what's supposed to be the lucee (official) light image.
Copy code
docker run --rm -d -p 8888:8888 -e LUCEE_ADMIN_PASSWORD=admin lucee/lucee:5.4.6.9-light-tomcat9.0-jdk11-temurin-jammy
http://localhost:8888/lucee/admin/server.cfm?action=ext.applications
attn: @justincarter , @micha
s
those are def not in the lucee light war we use
although we use commandbox to install it from a war and not the docker image
j
i'm coming from an earlier light version, which is as clean as it ought to be.
s
ah, got it
I will say, similar to separating extensions from my code, I also don't really like having the JDK bundled with the lucee image. I prefer the commandbox route for maximum control over each of those things
👍 1
j
i have a feature branch for a migration to the commandbox image which is most of the way complete but it was taking a long time to migrate all of the little bits over. so that's on pause.
note: the official image i'm coming from is
5.4.3.2-light-tomcat9.0-jdk11-temurin-jammy
, and that image is actually light.
q
@jamiejackson -- there is a ticket open about the some of the lite and zero docker images in the 5.4 train that actually had all the default plugins. I know they fixed it in 6.0.x, 6.1.x and 6.2.x.
j
maybe @justincarter?
i'm about 4 hours into trying to build my own multi-arch image based on the lucee-dockerfile repo and its
build-images.py
solved after 5 hours. i wasted about an hour of that time trying to build on mac. i was able to build on linux. it would be nice to solve this problem in the official images. multiply my 5 hours times anybody else who has to do this in the future and that's a lot of time spent.