Copy link to clipboard
Copied
I am trying to start up a development Coldfusion 2023 server using Docker that can run PDFg. I found the file https://github.com/carehart/awesome-cf-compose/blob/master/cf-2021-with-addons/compose.yaml and updated the images to CF2023.
My first attempts at starting these servers had both services start up. But the main coldfusion service contantly "Checking addons startup status". I also didn't see the addons server listed under the PDF Service tab.
After some experimentation I moved the - installModules above the -configureExternalAddons. This may be needed because I had to update the list of modules to be "all" due to the way our prod and test servers are set up. With this change the coldfusion server started up and was able to verify the PDFg Server status.
At this point I used Docker Desktop to stop my container so I could work on another project. When I came back to this project I used the Desktop to start the container. The coldfusion container started up and produced a warning pertaining to the addon server:
"addons: Temporary failure in name resolution http://addons:8995/PDFgServlet/".
I assumed this was because the addon server was not running in the desktop. I tried to manually stat the addon service. It immedialty stopped. No message other than "Skipping Addon Service setup" which would seem approriate as the service had already been set up. I tried again after giving the CF server time to get fully started. Same thing. I tried adding a restart policy to the addon service. It just churned.
At this point things work fine as long as I do an up vs a start. But this is exremly inconvenint and not really the way that docker enviornments are supposed to work.
I'm reaching out to see if anyone else has had this issue before and knows how to solve it.
Or is it just something that we have to put up with since the addon services were removed from the main CF image?
I am only using the PDFg addon so if there is a way to construct the yml file without needing the seperate service I am fine with that as well.
Copy link to clipboard
Copied
I'll try to create a cf2023 update of that specific compose file, and will confirm it works then will post it in the repo.
As for yo/down vs stop/start, I hear you feeling the latter is more common. I've not experienced that, but we can have differing opinion. I'll also try to test doing that, in case I might learn anything to help you with. Or perhaps someone else already will know.
Finally, it's not new that the pdfg has been in a separate service. It's always been since it (and cfhtmltopdf) came out in cf11. More important to your concern here, it's been a separate process launched within the container setup since Adobe created the docket images originally with CF2016.