I’ve launched the containers as follows:
docker run -d --name="pgjira" \
--network=host \
-e PGPROT=15432 \
-e POSTGRES_PASSWORD=1234 \
-e POSTGRES_DB=pgjira \
-e POSTGRES_HOST_AUTH_METHOD=md5 \
postgres:14
docker run -d --name="jira" \
--network=host \
-e JVM_MINIMUM_MEMORY=1024m \
-e JVM_MAXIMUM_MEMORY=2048m \
-e ATL_JDBC_URL=jdbc:postgres://localhost:15432/pgjira \
-e ATL_JDBC_USER=postgres \
-e ATL_JDBC_PASSWORD=1234 \
-e ATL_DB_DRIVER=org.postgresql.Driver \
-e ATL_DB_TYPE=postgres72 \
-e TZ=Asia/Seoul \
atlassian/jira-software:9.4-jdk11
However, I encountered a ‘couldn’t connect’ message after that, as shown in the attached image.
So, I removed(used prune in case) the above jira container and relaunched Jira without JDBC environment variables as follows:
docker run -d --name="jira" \
--network=host \
-e JVM_MINIMUM_MEMORY=1024m \
-e JVM_MAXIMUM_MEMORY=2048m \
-e TZ=Asia/Seoul \
atlassian/jira-software:9.4-jdk11
Then, I confirmed that the connection was successful when I entered information such as localhost, 15432, pgjira, postgres, 1234, etc. step-by-step through the UI.
From what I see, it seems that Jira’s DB initialization does not proceed just by entering the DB environment variable values.
Is there a way to enable such provisioning or automation when installing Jira with Docker?
+ Is there a way to enter the trial license during the Docker run process?
Hello 👋
i would try using -e PGPORT (postgres port) instead of -e PGPROT (seems like a typo to me). Also, as far as I remember the postgres standard port is 5432. But that number can be changed on PG side iirc so 15432 might be by design.
Oh! There was a typo....haha. Thx for noting it to me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.