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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,557,735
Community Members
 
Community Events
184
Community Groups

Confluence Docker container not starting

Edited
Pankaj Jangid
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 20, 2023

I am launching confluence using the docker-compose setup. Following is my setup:

Screenshot from 2023-03-21 11-30-41.png

It produces following error:

Screenshot from 2023-03-21 11-31-47.png

 

1 answer

By default the Confuence application runs as the user confluence, with a UID and GID of 2002,

Jira is 2001, make sure the data directory's owner is 2002 or 2001.

Pankaj Jangid
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 24, 2023 • edited

Initially, I have no directories. So directories are created by `docker compose up`. I don't know why the directories are created with root ownership. Even if I pass `user: confluence`, the host directories are still owned by `root`.

Another point, if I use named volumes then it works fine. but I want to use host directories.

When "docker compose up" creates the directories it makes they owned by root. You should create the directories before starting the containers and make them owned by the user that will have to use them inside the container. In this case, since it's for Confluence, you need to make they owned by uid 2002. Something like this:

mkdir -p ./logs/confluence-logs

sudo chown 2002:2002 ./logs/confluence-logs

Like Pankaj Jangid likes this
Pankaj Jangid
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 24, 2023 • edited

This works. I have also tried to pass `user: jira` in `docker-compose.yml` service definition. But that didn't work. This should ideally be fixed in the docker image. The entry-point script that is creating those folders should fix the ownership.

I would reference the vendor supplied Dockerfiles and perform similar chown/chmod actions:

https://bitbucket.org/atlassian-docker/docker-atlassian-jira/src/master/Dockerfile

Like Pankaj Jangid likes this
Pankaj Jangid
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 24, 2023

Thanks. I would definitely like to fix this.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS
AUG Leaders

Atlassian Community Events