portal entry

It would be really helpful to have the CF2018 beta as a container. It was also mentioned in a previous thread that an example apache container integrating the connector to CF would be very helpful. Oh and MUCH more flexibility in the configuration / environment variables for JVM memory, DSN, secure profiles, specific CF settings etc. etc.

Comment by Doug Cain

Thanks for the feedback. I will pass this to the engineers. We will also evaluate CF 2018 beta as a container. Certainly, useful.

Comment by Rakshith Naresh

Doug, if you want to use a containerized version of the 2018 beta, you can do so right now using the Ortus Docker images. They are powered by CommandBox, and therefore can start any CF engine/version and also come with CFConfig to manage all your config settings without needing to touch the admin UI and add-in modules like FusionReactor. You are free to wait for Adobe to come out with official images of course, but in the mean time this might give you something to play with.

Comment by Bradley Wood

Hi Brad, Thanks for that, I have used them before but we suffer from the ADCF war whitespace issue which makes it a bit tricky. I'll revisit what broke and see if we can fix it on our side, meantime I create my own CF containers for our dev environment which is quite a mission given the state of Adobes installers and config options.

Comment by Doug Cain

Oh just looked and adobe have updated their containers to include 2018 now by the look of it: https://bintray.com/eaps/coldfusion/cf%3Acoldfusion Wonder if they have addressed the config issues.

Comment by Doug Cain

Hi, i also have question on config, how could i pass serial no/license key to container? or somewhere have a detail document. Thank you. I have same question on forum: https://forums.adobe.com/message/10583687#10583687

Comment by Gordon Luk

Doug, Configuration can be provided by taking the CAR migration route, as in the ColdFusion 2016 containers. I understand your standpoint. we are exploring if the workflow can be improved.

Comment by Immanuel Noel

Gordon, As of today, licence can be provided from the administrator only. We are exploring if a key can be picked up from a config / environment file. We are working on documenting the container workflows, the way all features of ColdFusion are documented.

Comment by Immanuel Noel

Hi Immanuel, Thanks for info. about your team are exploring the workflow of container pick up license key. Wait for your good news. Thanks.

Comment by Gordon Luk

There seems to be a problem with this CF container. I run 3 instances, mapped the ports so that the local ports incremented but the internal ports (inside the container remained 8500) e.g. 8501->8500 but it seems only the first instance is accessible. SO you cant seemingly have N instances on the same docker host?

Comment by AdobeProductsUser

All I see in the other instances is endless log messages like this [000] Checking server startup status... [000] Checking server startup status... [000] Checking server startup status... [000] Checking server startup status... [000] Checking server startup status... [000] Checking server startup status... [000] Checking server startup status... [000] Checking server startup status... [000] Checking server startup status... [000] Checking server startup status... [000] Checking server startup status... [000] Checking server startup status... [000] Checking server startup status... [000] Checking server startup status... [000] Checking server startup status... [000] Checking server startup status... [000] Checking server startup status... [000] Checking server startup status... [000] Checking server startup status... [000] Checking server startup status... [000] Checking server startup status... [000] Checking server startup status...

Comment by AdobeProductsUser

Amir, could we have a look at your docker-compose file, if that's how you are running three separate containers? Ideally all three containers must run independently. You can reach out to me at inoel@adobe.com

Comment by INoel

Any update for the license key deployment workflow? Thanks

Comment by Gordon Luk

Is there a way to run/set ColdFusion's Apache Connector option with the ColdFusion container ?

Comment by dreynaud

On AWS, an auto-scaling configuration of CF on EC2 VMs can comply with CF licensing requirements by starting with an AMI that includes an hourly CF licensing fee (which varies by EC2 instance size). Adding/removing CF EC2 instances from the load balancer presents no CF licensing problems. On Azure, I see no availability of a machine image for CF, so it would appear to not be possible to have an auto-scaling configuration on Azure where licensing cost tracks usage. It would be necessary to purchase [n] CF licenses ahead of time and limit the number of machines in the cluster to the number of licenses purchased, which is far from optimal for peaky loads. I'm now considering a move to an auto-scaling config of Docker containers running CF, but how would one stay in compliance with CF licensing on either AWS or Azure? I see no availability of a CF container image on either platform, let alone one that includes an hourly licensing fee. Is there a plan to address this in the near future?

Comment by rcexpo

In case anyone else is interested in the answer, I had also emailed Rakshith, to which he replied: <em>Thanks for reaching out.</em> <em>I agree that we only have the AMI today. We are yet to offer an image on Azure.</em> <em>For containers, a perpetual CF Enterprise license will let you use it on any number of containers as long as the number of VCPUs is less than or equal to 8.</em>

Comment by rcexpo

There is a change in licensing quoted above. It is actually 8 containers per enterprise license. It is clarified here: <a href="https://helpx.adobe.com/coldfusion/enterprise/faq.html" rel="nofollow">https://helpx.adobe.com/coldfusion/enterprise/faq.html</a> Sorry about the confusion.

Comment by Rakshith Naresh

It doesn't seem anyone ever came back and updated this discussion. You can indeed now pass in the CF license key as an environment variable. For that and much more, see <a href="https://helpx.adobe.com/coldfusion/using/docker-images-coldfusion.html" rel="nofollow">https://helpx.adobe.com/coldfusion/using/docker-images-coldfusion.html</a>.

Comment by Charlie Arehart

I realize this is old, but in case others come upon this later, I'm pretty sure Gordon's Nov 2018 comment here was referring here to when there was no Docker image environment variable for passing in a CF license key/serial number. That was subsequently resolved, and there is indeed a "serial" env var now. For more, see the <a href="https://helpx.adobe.com/coldfusion/using/docker-images-coldfusion.html" rel="nofollow">page documenting use of the CF Docker images</a>.

Comment by Charlie Arehart

Are there any plans to add CF Docker Image in MS Azure?

Comment by ubhimani

Will this ever be properly documented?   What do all these env settings do? Why does the container start up in migration mode? It's a container - there will never be a migration <span></span>

Comment by Jim Priest

<p>Jim, I can’t tell if you’ve seen it but there is a page documenting those env vats, as well as showing use of the images, and including compose file showing various integrations. It’s at <a href="https://helpx.adobe.com/coldfusion/using/docker-images-coldfusion.html" rel="nofollow">https://helpx.adobe.com/coldfusion/using/docker-images-coldfusion.html</a>, and that is linked to from the Readme tab of the cf image bintray page above, though it could be made more clear.</p><p>As for your second point, and for those not understanding his meaning, he’s referring to how when you launch the admin the first time (within a container), you see the prompt one always would on first launch of the admin after an install. That cf admin code simply has not been changed to work differently, though it could.</p><p>(I can confirm that using the /data folder and car mechanism, discussed on that page above, the process STILL would show the migration page on first admin launch.)</p><p>Then again, one may not need to launch the admin, as the settings can be configure at container startup via either car files or a setup script, both discussed in that link in shared. </p><p>And cf2020 will change things even more with its new json-based cf setup feature, mentioned in the Dev week keynote yesterday (and previously).</p><p>And fwiw, I will be doing a Dev week talk on Friday on getting started with the cf docker images. It’s a revision and expansion of one I did at cf summit 2019, available online.</p><p>Note also the recent post here from Dave Byers, 2nd in a series on his take on getting started.</p><p>I’ll come back and edit this comment to add links. Challenging in the tiny window in the mobile ui for these blog comments.</p>

Comment by Charlie Arehart