Skip to main content
J
John Blayter
Participant
May 23, 2024
Question

ColdFusion won't start in Docker Container

  • May 23, 2024
  • 2 replies
  • 699 views

I am having an issue where the ColdFusion service inside of the Docker Container is not starting up. When I look at the Logs view in Docker Desktop all that returns is the following.

 

 [] Checking server startup status...

 

 

This setup has been working for months and all of the sudden after the 14.5 update on MacOS it stopped working. 

 

Chipset: Apple M3 Max

MacOS 14.5

Docker Desktop Version 4.30.0 (149282)

Docker Engine: 26.1.1

 

Docker Container Setup Script

 

# variables
cf_administrator_pwd=ColdFusion123

# Run the docker conainer
docker run -dt --name mysite -p 80:8500 -v $PWD/www:/app -e acceptEULA=YES -e password=$cf_administrator_pwd -e enableSecureProfile=true --platform linux/amd64  adobecoldfusion/coldfusion2023:latest

# Wait 10 seconds
sleep 10

# Install All
docker exec mysite /opt/coldfusion/cfusion/bin/cfpm.sh install all

 

 

When I look at the logs in the container I am seeing that ColdFusion is started 
/opt/coldfusion/cfusion/logs/coldfusion-out.log

 

May 23, 2024 19:20:57 PM Information [main] - ColdFusion started
May 23, 2024 19:21:00 PM Information [main] - ColdFusion: application services are now available

 

 

The error log does have some things that do look weird for sure (attached)

 

 

 

I've tried everything that I can think of and I am at a complete loss. 

    This topic has been closed for replies.

    2 replies

    J
    John BlayterAuthor
    Participant
    May 23, 2024

    Hey Charlie, been forever man! I ended up doing the unthinkable and nuked my Mac and rebuild from the 14.3.1 OS build and Docker Desktop 4.29.0 and that setup worked 100%. I did try uninstalling Docker when I was on Mac OS 14.5 and downgrading to the 4.29.0 version and that also didn't work. I am going to let this sleeping dragon sleep and not mess with it. 
    I am going to try building off of specific tags in the future as well for stability. Seems to be a better approach when I think about it. 

    Charlie Arehart
    Community Expert
    Charlie ArehartCommunity Expert
    Community Expert
    May 23, 2024

    Glad to have helped, though I'm surprised you took that drastic step when I'd replied within 2 hours of your post. :-(. Perhaps the info may help others finding this in the future. 

     

    One more thing: you show calling the cfpm script to add all modules. Were you aware that the cf images since 2021 offer an env var to import the modules, called installModules? It also supports "all", as a value. More at https://helpx.adobe.com/coldfusion/using/docker-images-coldfusion.html

    /Charlie (troubleshooter, carehart. org)
    Charlie Arehart
    Community Expert
    Charlie ArehartCommunity Expert
    Community Expert
    May 23, 2024

    John, I appreciate how frustrating it can be when cf won't start (in a container or not). And thanks for sharing the coldfusion-error.log. That's vital for some problems.

     

    You say the problem started all of a sudden, when "after the 14.5 update on MacOS it stopped working."

     

    Someone else may want to suggest this an issue related to whether cf supports your macos version or the m3 processor, though I'm not positive that's the issue. First, you mention what you moved TO, but can you tell us also what you came from (different macos version? Different processor? Different docker desktop version?)

     

    Second, you show referring to the "latest" tag, which doesn't always mean you'll get THE latest version, since docker caches what you got in the past. I'm curious if it may work differently with a more recent image. If you change to using  adobecoldfusion/coldfusion2023:2023.0.6, does that change things? (I've not proposed .0.7 because that introduces a breaking change unrelated to this problem.) 

     

    As for the key error, it seems to be this one:

    Caused by: java.util.zip.ZipException: ZipFile invalid LOC header (bad signature)

     I don't think that's related to the "zip" problem from last year introduced when the jvm running cf is changed and a cf update is applied. I'll assume you have not done either of those. (And such a cf update is unnecessary with the available tags for different versions.) 

     

    There are more diagnostics to consider, but let's hear what you report on the things I've asked above.  Or maybe someone else will have a different suggestion. 

    /Charlie (troubleshooter, carehart. org)
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices