Copy link to clipboard
Copied
Dear,
I am running docker swarm mode clustering. When docker created new coldfusion container, how could auto-pass serial number on it? or have it a variable on setupColdFusion.cfm? Thanks.
Copy link to clipboard
Copied
Gordon, that's an interesting question. You don't say having looked at it, but the "readme" for the Adobe CF docker containers at https://bintray.com/eaps/coldfusion/cf%3Acoldfusion#read does in fact show how to pass in startup variables to the container. But curiously it makes no mention of passing in the license key. (And I saw no places there to ask questions.)
If you don't get an answer here, there was an Adobe blog post announcing the containers, https://coldfusion.adobe.com/2018/05/docker-images-for-coldfusion/, and Adobe folks have answered questions asked there in the comments. You could ask there also.
Or maybe someone else has already solved this and can chime in here.
Copy link to clipboard
Copied
Dear Charlie, thanks for your info. I will ask the same question on the blog post as well.
Copy link to clipboard
Copied
As Adobe only provides binary files, it's not possible to see all variable docker exposes. 😞
Copy link to clipboard
Copied
Dear All,
Adobe engineer replied they are exploring the workflow. It can't pass license to container at the moment. :~(
Copy link to clipboard
Copied
Since the last message in this thread in 2018, Adobe had added the ability to pass in the license key as an environment variable, among other vars as well. They are documented in this page with lots more info:
https://helpx.adobe.com/coldfusion/using/docker-images-coldfusion.html​
BTW, bardnet had said earlier, "As Adobe only provides binary files, it's not possible to see all variable docker expose", with the implication being that unless Adobe documented what the env vars were, we'd have no way to know. That's not so.
First of all, if you call run images with a help command, they will show their env vars. Second, one could start the image, then do a docker EXEC to run bash and look in the root of the image to see the startup script, which is plain text showing how the env vars are processed. 🙂