tracker issue : CF-4205335

select a category, or use search below
(searches all categories and all time range)

CF2018 Docker image "cli" command (REPL) fails, sends container into 100% cpu spin

| View in Tracker

Status/Resolution/Reason: To Fix//Investigate

Reporter/Name(from Bugbase): Charlie A. / ()

Created: 09/28/2019

Components: Containers, CF Docker Image

Versions: 2018

Failure Type: Incorrectly functioning

Found In Build/Fixed In Build: n/a /

Priority/Frequency: Normal / Some users will encounter

Locale/System: / Windows 10 64 bit

Vote Count: 0

The CF Docker images offer a "cli" command, and in 2018 it is supposed to run the new CF2018 REPL, and I know I have used it in the recent past, but recently on two machines I am finding that if I simply try to start the image with the CLI, it fails with errors, a nullpointer, and the CPU for the container spins to 100% (per the Docker Stats) command.

Here's what should work (again, optionally with a volume specified, but I thought it worked before without it, and it still has the same problem if I DO specify a volume):

docker run --rm -e acceptEULA=YES cli

I will get first an error (if I don't specify a volume for the /app folder), then (either way) it tries to start the interactive mode, then I get the nullpointer exception:

/opt/startup/ 441: cd: can't cd to /app
ColdFusion started in interactive mode. Type 'q' to quit.

And that NPE error repeats indefinitely, until I terminate/dettach from the container, with ctrl-C.

But that alone does not stop the impact. The image continues to run and again uses up to 100% CPU as seen in the Docker stats command (and the whirring of my laptop fan).

Can anyone else run that command above, to see if it works ok for them? If it does, as the help shows you, you can use q to quit, which exist the container.



Folks, what's the response to this? I see you have changed it to reason code:investigate. Can anyone else (Adobe or otherwise) confirm seeing the same issue? BTW, you can see it happen in Once the image downloads, the errors will appear. And if you SSH into the server (via the SSH link offered at the pwd site), you can see that the CPU of the CF process goes through the roof. This is NOT a problem on my own machine, and it should happen to anyone. Can someone confirm seeing it? And can someone from Adobe address it? Thanks.
Comment by Charlie A.
31667 | October 21, 2019 05:06:03 PM GMT