Coldfusion 2025 cfsetup CustomTag Import Error

[Kenneth36360521ynm9]

Hello,

I have installed coldfusion 2025 over docker, i have configure everything and import all settings except for one, CUSTOMTAGS it is not working on any way, see image attached, a fresh export cant be imported back, idk if im doing something wrong but it is not even working with a fresh install.

this is the export of the cfsetup for

docker-compose

services:
  cf2025:
    image: adobecoldfusion/coldfusion2025:latest
    container_name: cf2025
    ports:
      - "8511:8500"
    environment:
      acceptEULA: "YES"
      importCFSettings: /app/config/settings.json #same error as with customtag.json for customtags section
      installModules: "debugger,mail,oracle"
    volumes:
      - /webdata/coldfusion:/app

customtag.json

{"CUSTOMTAG":{"/WEB-INF/customtags10000":"/opt/coldfusion/cfusion/CustomTags","/WEB-INF/customtags1755704070605":"/app/shared"}}

Regards,

Ken

[Kenneth36360521ynm9]

Image

[Charlie Arehart]

Kenneth, a few questions:

1) in your volume "/webdata/coldfusion", what files do you show there (from the host perspective, I mean)? And have you gone into the container to confirm that the /app folder matches it? 

2) And is that a volume mount (a folder on the host) or a true Docker volume? and is the host running Windows or Linux? It can help with me asking some follow-ups.

3) And as for that customtag.json, I don't see that you're referring to it in your compose. You show using only settings.json. Anyway, is that settings.json in both places: the volume and the /app folder within the container? It needs to be in the latter for your importCFSettings to work. 

4) And have you confirmed (via the admin within the container) whether whatever you configured using that import did appear? If you may only be "running the app code, which doesn't work as expected", take the time to add the password env var in your compose so you can login to check it out. (I realize you or others may prefer "never to go into the CF Admin within the container". This is for diagnostic purposes, not for manipulating the container.) 

5) Finally, as for those values you show being within your customtag.json, where did those come from? a cfsetup export? Was that done from within the container? Why would you be doing that? Don't you want the custom tag paths to be passed in on that import? Do you have customtags defined within that settings.json or not?

You show the customtag.json currently having:

{"CUSTOMTAG":{"/WEB-INF/customtags10000":"/opt/coldfusion/cfusion/CustomTags","/WEB-INF/customtags1755704070605":"/app/shared"}}

That first one being in /opt/coldfusion/cfusion/Customtags would be the one CF sets up by default, whereas the second one showing /app/shared implies that you plan to put some cf custom tag templates into that /app/shared folder. Do you have such code in that folder?

[Kenneth36360521ynm9]

Hello Charlie,

1. Yes both matches and it contains my shared folder, it propagates correctly host - container

2. Host is linux and /webdata/coldfusion is bind to /app  not a true docker volume

3. I dont refer to customtag.json as it is already on settings.json the custom tag section is the same as the one I pasted, it was just a only section export to verify if import was failing.

4. everything else i have on the settings.json gets imported, the only one that fails is the CustomPaths, everything else gets imported sucessfully when I start the docker container.
5. The values showed on the customtag.json is a single export of that particular section, it is the same i have within settings.json and yes it is an export from within the container after manually setting it up.

I do plan to use /app/shared as my custom templates as all of our shared components for multiple apps are there.  I want to basically convert our current production deployments to docker to facilitate our migrations.  I could provide the docker logs tomorrow.

Thanks for your response 

[Charlie Arehart]

Ok, so you're just focused on an inability to import customtag paths, whether a) via the importCFSettings env var (and in the file it points to), or b) even via cfsetup import run within the container, where as a sanity check you'd manually defined it and exported it--and STILL can't import it.

One thing: don't bother with the first path. Again, it's always built-in.  See if that helps. (I'm writing from a phone so can't easily test this for you.)

Second, do you run cf on the Linux host? What if you configure and export a customtag path there? Can you import it there? (Again, try taking out the first one.) If that fails, then this isn't about the cf docker image at all, but about the cfsetup tool. To be clear, all the importCFSettings does is cause that very tool to be called during container startup.

And along this lines, please confirm what is the cf update you're running. You can find it in the admin on both the host and container.

And don't presume the container is 2025 update 3, simply because you use adobecoldfusion/coldfusion2025:latest. Your docker host environment could have cached that for some earlier run of this compose file. Once you've confirmed the version, you could do a `docker pull adobecoldfusion/coldfusion2025:latest`, which WOULD pull down the image for update 3 if you didn't already have it.

I'm just saying we want to be at the latest update for both the host and the image before perhaps reporting this as a bug.

BTW, if you "just need to get this containerization working ASAP", you don't HAVE TO use the importCFSetrings env var. That was added in cf2021. 

You could instead export the one customtag in a CAR file (from the host, in the cf admin packaging page), or via code you write to create the custom tag path using the CF admin api. See the cf docs on the cf docker image which shows how to import either of these to be run on container startup. I also show examples of doing each in my "awesome cf compose" repo at github.

Let us know what above does or doesn't work for you. 

[Kenneth36360521ynm9]

Hello Charlie,

Yes, I can confirm I’m unable to import customtags via either of the methods you mentioned. My Docker image is the latest build, and I’ve already pruned/cleaned all images and containers to make sure nothing old is lingering. I’ve also tested with the same version on a plain Linux installation outside of Docker, and the import still fails. I even tried removing the default customtag line (the first path) in the JSON, but no luck.

I’ll take a look at your repo and the CAR File approach you suggested and get back to you. At this point though, I’m leaning toward it being a bug, since I’ve hit the same issue across environments.

[Kenneth36360521ynm9]

Hello Charlie,

We managed to user the CAR file to make a migration, it was successful.  But we needed to add our CustomTags path as a Directory Mapping, i did not see them anywhere added on the CAR creation nor on the new deployment upon CAR import, everything else was there, DBs and all.  The issue remains, when importing CustomTags paths via settings.json with CustomTags error and via CAR they are not considered.  For now we went with the Mapping.  Thanks