http://coldfusion.com logo
Join Slack
Powered by
<@U06V253M4> how does this look to you? <https://g...
# cfml-general
z
b
@zackster The maintainers of the project (in the past, at least) don't like open ended versions which can change between runs
They prefer to have everything pinned and then manually update for each version
it's a pain, but they don't want the software versions changing between runs
z
ok, so i need to pin them, which commandbox image
3.13.1 yeah?
b
yeah, and the Lucee version too
I don't know what the latest image is, but whatever tags you see on docker hub should be it
z
docker hub was confusing, this is ok to follow yeah? https://github.com/Ortus-Solutions/docker-commandbox/tags
b
I'm not actually sure exactly how the Git repo tags align with the actual Docker image tags. We have a whole bunch of docker tags we create. @jclausen can probably clarify
z
good to know, i was a bit confused
b
The last run of our docker builds was 9 days ago, which produced 2 full pages of tags on docker hub, and for the life of me, I can't find a single one that looks like 
3.13.1
like the readme suggests
z
getting all this and the fail, any ideas?
Copy code
cfml: [INFO] 2025-05-08T19:01:24Z runwar.context - 2025-05-08 19:01:24 cachebox.system.cache.providers.CacheBoxColdBoxProvider Reaping scheduled task started for default cache.
cfml: [INFO] 2025-05-08T19:01:24Z runwar.context - 2025-05-08 19:01:24 cachebox.system.cache.providers.CacheBoxColdBoxProvider CacheBox Cache: default has been initialized successfully for operation
cfml: [INFO] 2025-05-08T19:01:26Z runwar.context - 2025-05-08 19:01:26 cachebox.system.cache.providers.CacheBoxColdBoxProvider Reaping scheduled task started for default cache.
cfml: [INFO] 2025-05-08T19:01:26Z runwar.context - 2025-05-08 19:01:26 cachebox.system.cache.providers.CacheBoxColdBoxProvider CacheBox Cache: default has been initialized successfully for operation
cfml: [INFO] 2025-05-08T19:01:27Z runwar.context - 2025-05-08 19:01:27 cachebox.system.cache.providers.CacheBoxColdBoxProvider Reaping scheduled task started for default cache.
cfml: [INFO] 2025-05-08T19:01:27Z runwar.context - 2025-05-08 19:01:27 cachebox.system.cache.providers.CacheBoxColdBoxProvider CacheBox Cache: default has been initialized successfully for operation
cfml: [INFO] 2025-05-08T19:01:29Z runwar.context - 2025-05-08 19:01:29 cachebox.system.cache.providers.CacheBoxColdBoxProvider Reaping scheduled task started for default cache.
cfml: [INFO] 2025-05-08T19:01:29Z runwar.context - 2025-05-08 19:01:29 cachebox.system.cache.providers.CacheBoxColdBoxProvider CacheBox Cache: default has been initialized successfully for operation
cfml: [INFO] 2025-05-08T19:01:31Z runwar.context - 2025-05-08 19:01:31 cachebox.system.cache.providers.CacheBoxColdBoxProvider Reaping scheduled task started for default cache.
cfml: [INFO] 2025-05-08T19:01:31Z runwar.context - 2025-05-08 19:01:31 cachebox.system.cache.providers.CacheBoxColdBoxProvider CacheBox Cache: default has been initialized successfully for operation
cfml: [INFO] 2025-05-08T19:01:33Z runwar.context - 2025-05-08 19:01:33 cachebox.system.cache.providers.CacheBoxColdBoxProvider Reaping scheduled task started for default cache.
cfml: [INFO] 2025-05-08T19:01:33Z runwar.context - 2025-05-08 19:01:33 cachebox.system.cache.providers.CacheBoxColdBoxProvider CacheBox Cache: default has been initialized successfully for operation
cfml: [INFO] 2025-05-08T19:01:34Z runwar.context - 2025-05-08 19:01:34 cachebox.system.cache.providers.CacheBoxColdBoxProvider Reaping scheduled task started for default cache.
cfml: [INFO] 2025-05-08T19:01:34Z runwar.context - 2025-05-08 19:01:34 cachebox.system.cache.providers.CacheBoxColdBoxProvider CacheBox Cache: default has been initialized successfully for operation
cfml: [INFO] 2025-05-08T19:01:36Z runwar.context - 2025-05-08 19:01:36 cachebox.system.cache.providers.CacheBoxColdBoxProvider Reaping scheduled task started for default cache.
cfml: [INFO] 2025-05-08T19:01:36Z runwar.context - 2025-05-08 19:01:36 cachebox.system.cache.providers.CacheBoxColdBoxProvider CacheBox Cache: default has been initialized successfully for operation
cfml: [INFO] 2025-05-08T19:01:38Z runwar.context - 2025-05-08 19:01:38 cachebox.system.cache.providers.CacheBoxColdBoxProvider Reaping scheduled task started for default cache.
cfml: [INFO] 2025-05-08T19:01:38Z runwar.context - 2025-05-08 19:01:38 cachebox.system.cache.providers.CacheBoxColdBoxProvider CacheBox Cache: default has been initialized successfully for operation
cfml: [INFO] 2025-05-08T19:01:39Z runwar.context - 2025-05-08 19:01:39 cachebox.system.cache.providers.CacheBoxColdBoxProvider Reaping scheduled task started for default cache.
cfml: [INFO] 2025-05-08T19:01:39Z runwar.context - 2025-05-08 19:01:39 cachebox.system.cache.providers.CacheBoxColdBoxProvider CacheBox Cache: default has been initialized successfully for operation
Framework http4k does not define a default test in benchmark_config.json
Framework hyperlane does not define a default test in benchmark_config.json
Framework oak does not define a default test in benchmark_config.json
cfml: ERROR: Framework is not accepting requests from client machine
cfml: Total test time: 3m 47s
tfb: Total time building so far: 2m 38s
tfb: Total time verifying so far: 0s
tfb: Total execution time so far: 3m 51s
cfml: Total TCP sockets: 33
================================================================================
Parsing Results ...
================================================================================
Framework http4k does not define a default test in benchmark_config.json
Framework hyperlane does not define a default test in benchmark_config.json
Framework oak does not define a default test in benchmark_config.json
b
No, not sure. I'd say the container isn't starting, but their testing setup can be a bit of a pain to use
It's been a hot minute since I did anything with it
j
ortussolutions/commandbox:3.13.2
will get you CommandBox 6.2.0 running on Ubuntu Noble. The changelog has the association with the CommandBox version and will tell you when engine versions were updated, etc.
👍 1
I’ve got to push a release with CommandBox 6.2.1 this week.
Depending on which engine you are using and which framework, you’ll need to ensure the modules necessary are installed too. I would suggest taking a look at the individual server files coldbox uses for the different engines to determine what modules or extensions might be necessary to get things running.
b
Zac is just updating the existing docker files for the techempower benchmarks. All of the warmup and extensions are handled when I set this up years ago. He's just trying to bump the versions to be the latest available
👍 1
z
is java 24 ok?
b
CommandBox is still bundling Lucee 5.4. Is it OK on Java 24?
I've used java 21 with no issues, but haven't tested a ton past that yet
z
more or less, i'm trying with 21, still a world of pain
cfml: mv: cannot stat '/app/server-start.sh': No such file or directory
j
We have a JDK 24 version of the commandbox image you can test with: 
ortussolutions/commandbox:jdk24-3.13.2
It does pass the basic tests but I’ve not tried it.
b
I'd guess something in the how the base image has changed between the older docker image I was using before and the one you're using now
z
runs fine off master
j
Copy code
cannot stat '/app/server-start.sh': No such file or directory
In my experience, this error almost always indicates a fatal error occurred when CommandBox tried apply settings in a CFConfig file or in a 
server.json
file. For example - a bad path to a config or rewrite file
z
for 6 it should be luceeServer i guess? but then it wants a to
j
Copy code
ENV box_server_runwar_args=--cache-servlet-paths=true
Commandbox 6 also changed how runwar args are handled. I’m not sure that one is supported any more.
z
yeah that's now under options instead of args
j
You can also just name that web config 
.cfconfig-web.json
and CommandBox will automatically pick it up on start for the web context
z
Copy code
cfml: Step 1/12 : FROM ortussolutions/commandbox:3.13.2
cfml: Docker build failed; terminating
cfml: Traceback (most recent call last):
cfml:   File "/FrameworkBenchmarks/toolset/utils/docker_helper.py", line 53, in __build
cfml:     raise Exception(token['errorDetail']['message'])
cfml: Exception: manifest for ortussolutions/commandbox:3.13.2 not found: manifest unknown: manifest unknown
j
What version of Docker are you running?
z
4.41.1
j
Lol!
The current version is Docker 28!
z
j
Oh. The 4.41.1 is the version of Docker Desktop - not the docker engine.
Oh. Weird.
z
3.13.0 seems to resolve, that has jakarta support?
j
Yeah, that tag is bad somehow. You should be fine with 3.13.0
Looks like my tag builds failed, actually. Re-running them now: https://github.com/Ortus-Solutions/docker-commandbox/actions/runs/14667975309
z
look like it might be working.....
🚀 1
no dice, goign back to try with 21
lots of this
Copy code
cfml: [INFO] 2025-05-08T20:11:54Z runwar.context - 2025-05-08 20:11:54 cachebox.system.cache.providers.CacheBoxColdBoxProvider Reaping scheduled task started for default cache.
cfml: [INFO] 2025-05-08T20:11:54Z runwar.context - 2025-05-08 20:11:54 cachebox.system.cache.providers.CacheBoxColdBoxProvider CacheBox Cache: default has been initialized successfully for operation
cfml: [INFO] 2025-05-08T20:11:56Z runwar.context - 2025-05-08 20:11:56 cachebox.system.cache.providers.CacheBoxColdBoxProvider Reaping scheduled task started for default cache.
cfml: [INFO] 2025-05-08T20:11:56Z runwar.context - 2025-05-08 20:11:56 cachebox.system.cache.providers.CacheBoxColdBoxProvider CacheBox Cache: default has been initialized successfully for operation
cfml: [INFO] 2025-05-08T20:11:58Z runwar.context - 2025-05-08 20:11:58 cachebox.system.cache.providers.CacheBoxColdBoxProvider Reaping scheduled task started for default cache.
cfml: [INFO] 2025-05-08T20:11:58Z runwar.context - 2025-05-08 20:11:58 cachebox.system.cache.providers.CacheBoxColdBoxProvider CacheBox Cache: default has been initialized successfully for operation
cfml: [INFO] 2025-05-08T20:11:59Z runwar.context - 2025-05-08 20:11:59 cachebox.system.cache.providers.CacheBoxColdBoxProvider Reaping scheduled task started for default cache.
cfml: [INFO] 2025-05-08T20:11:59Z runwar.context - 2025-05-08 20:11:59 cachebox.system.cache.providers.CacheBoxColdBoxProvider CacheBox Cache: default has been initialized successfully for operation
cfml: [INFO] 2025-05-08T20:12:01Z runwar.context - 2025-05-08 20:12:01 cachebox.system.cache.providers.CacheBoxColdBoxProvider Reaping scheduled task started for default cache.
cfml: [INFO] 2025-05-08T20:12:01Z runwar.context - 2025-05-08 20:12:01 cachebox.system.cache.providers.CacheBoxColdBoxProvider CacheBox Cache: default has been initialized successfully for operation
cfml: [INFO] 2025-05-08T20:12:03Z runwar.context - 2025-05-08 20:12:03 cachebox.system.cache.providers.CacheBoxColdBoxProvider Reaping scheduled task started for default cache.
and i see images flash in docker desktop and disappearing
j
Yeah, I’m not a big fan of those loggging out at info with Coldbox ( I would rather those be debug ), but you will have to take that up with @lmajano 🙂
b
You can adjust the logbox logging to warn. I think we changed those logs to be debug a long time ago, but the version of ColdBox in this project is pinned to an older version
Either way, those logs don't indicate any sort of issues. They just show ColdBox is booted up and its caches are reaping
☝️ 1
l
Yea that's changed
z
ahhh, the above was the script erroring, the tfb feedback is confusing, it's swallowing and ignoring 500s
2 Views
Open in Slack
PreviousNext
Powered by