Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Confluence server in docker crashes during initialization during setuppaths.action


I'm trying to run an eval of confluence on Mac OSX using the atlassian confluence docker image from docker hub but as I go through the SetupWizard on localhost:8090, after the DB setup completes and I reach setup/setuppaths.action, the confluence server (and docker container) crashes consistently.

I've confirmed its not an issue with file/directory permissions with the mounted directory and I believe I've set the database up following the posted instructions.  The logs/atlassian-confluence.log doesn't appear to contain any errors.

Is this a known issue with my platform or database choice or.....?

Any insight on the issue would be appreciated.  Here are some additional details:

Docker image:

Docker run command:

docker run -v /tmp/data/confluence-home:/var/atlassian/application-data/confluence --name="confluence" --user 2002:2002 -d -p 8090:8090 -p 8091:8091 atlassian/confluence-server


Postgres 13

Database create command used:


The last line in the log prior to the crash is: 

"2021-04-13 20:31:08,350 INFO [Catalina-utility-1] [atlassian.plugin.manager.DefaultPluginManager] logTime Plugin system lateStartup ended"

If its useful, if I restart the docker container w/o cleaning up the contents of $CONFLUENCE_HOME, I get the following additional log entry:


com.atlassian.util.concurrent.LazyReference$InitializationException: java.lang.IllegalStateException: Spring Application context has not been set
    at com.atlassian.util.concurrent.LazyReference.getInterruptibly(

caused by: java.lang.IllegalStateException: Spring Application context has not been set
    at com.atlassian.spring.container.SpringContainerContext.getComponent(


1 answer

1 accepted

1 vote
Answer accepted

FYI....Got it working.  Turns out the memory recommendation on the site for the docker image ( is incorrect: "We recommend 2GiB of memory allocated to accommodate the application server."  docker stats shows it taking up 3GiB during initialization and during runtime.

That's good news Scott! Because this is exactly what I can trying to accomplish and also run into weird crashes and nothing ever booting. It just seemed to cycle.

I don't remember the cpu/memory limits I set but as assume they were too small as well.

Awesome :D Now I can try again! And thanks for sharing the docker run cmdline with your volumes and port mapping. That clears up another question I had!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Confluence

Confluence Mythbusters: Does Atlassian even use Confluence?

Hi, Confluence collaborators! As part of #Confluence-Collaboratory month, we’ve created a very special Mythsbusters segment, where we're dive into an interesting myth and uncover the truth behind i...

1,609 views 7 30
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you