Skip to main content
paulm1677332
paulm1677332
Inspiring
September 18, 2025
Question

Coldfusion 2023 on docker

  • September 18, 2025
  • 1 reply
  • 411 views

Hi,

We use docker locally and have an issue now with latest 2023 version. We are getting the following error wherever a component is called on a page which has a type on cfargument. Removing the type allows the page to load without error. The error we see is as follows

'coldfusion.runtime.Variable coldfusion.runtime.UDFMethod._validateArgWithValidator(java.lang.String, java.lang.String, coldfusion.runtime.Variable, coldfusion.tagext.validation.CFTypeValidator)'

java.lang.NoSuchMethodError: 'coldfusion.runtime.Variable coldfusion.runtime.UDFMethod._validateArgWithValidator(java.lang.String, java.lang.String, coldfusion.runtime.Variable, coldfusion.tagext.validation.CFTypeValidator)' at

We also see errors related to the image package where it says we need to install the image package but it's already installed. We've pulled most recent image, started stopped the container etc. but still seeing those issues. Nothing obvious showing in the logs. Anyone any ideas?

 

There was a version of Coldfusion 2018 running locally (not via docker) but was uninstalled. Just wondering if that might have an effect.

Thanks

1 reply

Charlie Arehart
Community Expert
Charlie ArehartCommunity Expert
Community Expert
September 18, 2025

Paul, which cf image are you using?

 

And are you saying it's you're first use of a cf2023 image? Or were things working before? If so, what changed? Did you maybe apply a cf update, such as with the cf2023 admin within the container? You ought to use the new image from Adobe (one is offered for each update).

 

(Failures like that can happen when one applies a cf update, where deleting the cfusion/bin/felix-cache and restarting cf can help. That's harder within a container, but not impossible. It's simply better to use new images with the new update baked in.)

 

Finally, no, nothing about processing cfml within the container would have ANYTHING to do with your having cf2018 installed on the host machine. You could potentially have PORT conflicts if both were running, but the error you show is not about that.)

 

Let us know what you find. 

/Charlie (troubleshooter, carehart. org)
paulm1677332
paulm1677332Author
Inspiring
September 19, 2025

Hi Charlie,

We're using the latest 2023 image which was updated 9 days ago I believe. It worked with the 2018 image but updated it to 2023 one (public.ecr.aws/adobe/coldfusion:latest-2023) and we get these errors. The package issue is also odd. Saying its not installed when it is. 

Paul

Charlie Arehart
Community Expert
Charlie ArehartCommunity Expert
Community Expert
September 19, 2025

Ok, so first it seems you're saying you did intentionally change from using the 2018 to the 2023 image. That's a big jump, of course. Even taking code running on a hosted cf2018 and switching to 2023 you could have errors, perhaps even that one.

 

I don't readily recognize it, as some generic one people get under a common scenario. Assuming no one else does, could you pare it down to a simple few-line demo? It need not even involve a cfc (if you're using one), since you could also define a function and call it in a single cfm.

 

Next, as for the image package, you may already know how that's new as of cf2021 (the notion of cf functionality being broken into packages/modules, which you can optionally install or not).

 

You say that the image package "is already installed". Are you asserting that because it shows that in the cf admin of the container, on its "package management" page, under "installed packages"?

 

More to the point, since you're working with containers, did you indicate the need of that package when you started the container? That's done by either of a couple of env vars. However you may be starting the container (from a dockerfile, a compose file, a kubernetes manifest, the docker run at the command line, or something else), are you specifically naming that package to be installed?

 

Finally, during the startup is when packages are managed,as tracked in the coldfusion-out.log. Do you see it showing setup of this image package (perhaps among others)? Note that with the cf images, for cf2021 and cf2023, there are actually a couple of cf startups per run of the container (such as to handle installing of packages, or other config specifications). So watch out for MORE than just the LATEST cf startup in the logs. (That problem was addressed starting with the cf2025 images.)

 

I realize you're likely wishing simply for a solution to what may seem to you to be a couple of clear bugs. I've not experienced them or helped anyone else hitting them, with the cf2023 images (over the past couple of years).

 

I hope some of these ideas might help, or you can wait to see what others may offer. (I'm writing from a phone, so can't readily setup tests of your two issues.) I'll look forward to your response and take it from there. 

/Charlie (troubleshooter, carehart. org)
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices