I am having a weird issue with installing a specif...
# lucee
d
I am having a weird issue with installing a specific version of the s3 extension. We have historically installed extensions by having a
LUCEE_EXTENSIONS
env variable. We specify the extension ID, name, and version. We’ve never had a problem until we started trying to install the latest version of the s3 extension (2.0.2.19). We have specified the following…
Copy code
LUCEE_EXTENSIONS="CED6227E-0F49-6367-A68D21AACA6B07E8;name=admin;version=1.0.0.5, D4EDFDBD-A9A3-E9AF-597322D767E0C949;name=oracle;version=21.3.0.0000, 66E312DD-D083-27C0-64189D16753FD6F0;name=pdf;version=1.2.0.10, 671B01B8-B3B3-42B9-AC055A356BED5281;name=postgresql;version=42.2.20, 60772C12-F179-D555-8E2CD2B4F7428718;name=redis;version=3.0.0.51, 17AB52DE-B300-A94B-E058BD978511E39E;name=s3;version=2.0.2.19"
I can see as the container starts up that it installs 2.0.2.19 but then “updates” to 2.0.1.25, which doesn’t have a ton of the s3 functions. I can go into the Admin after and update to 2.0.2.19 without a problem, and it even prompts me to update to the latest version, but that doesn’t work very well in a containerized environment. Has anyone seen something like this?
I tried an older version of s3 and it does the same thing. It installs the requested version then later removes it and forces 2.0.1.25.
Not installing the s3 extension via the LUCEE_EXTENSIONS env variable still results in Lucee installing v2.0.1.25 of the s3 extension. It seems to be bundled by default.
Is anyone using the latest version of the s3 extension in container land? How are you getting it installed?
Trying to get more eyes on it, I posted to
<http://dev.lucee.org|dev.lucee.org>
as well. https://dev.lucee.org/t/lucee-forcing-v2-0-1-25-of-the-s3-extension/14608
It looks like this is a bug that was fixed in 6.1. That’s great, but also not great since we are on 5.4. 🙁 https://luceeserver.atlassian.net/browse/LDEV-4996 https://luceeserver.atlassian.net/browse/LDEV-5004