cptactionhank / docker-atlassian-jira-service-desk Goto Github PK

Just a minor issue:
The link in the readme.md seems to be outdated. It is missing the "jira-" part of the link. Should be:
https://cptactionhank.github.io/docker-atlassian-jira-service-desk/

Thumbs up of for the repos!

Hi,
in line 13 of the Dockerfile the switch -g is used to add the user to group jira. -g stands for GECOS-Field. This only seems to be the case on busybox. (try adduser --help)
The switch for group is -G. In my case, the user was added to group nogroup and had no rights to open outgoing ports. I changed the line to "&& adduser -S -u 1000 jira -G jira " and everything works fine now.

Please replace FROM java:8 by FROM openjdk:8, as in this commit.

Is there any solution to persist /opt/atlassian/jira directory?

We want to mount it like /var/atlassian/jira to /opt/directory/jira-opt . & ../jira-var

May there is any issue with permissions on it? For /var the user-id inside the container works fine.

version: '2'

services:
  db:
    container_name: jira-servicedesk_prod_db
    image: postgres
    networks:
      - servicedesk
    volumes:
      - /opt/docker/04-jira-servicedesk/db:/var/lib/postgresql/data
    ports:
     - "5432"
    environment:
     - POSTGRES_USER=jiraservicedesk
     - POSTGRES_PASSWORD=password
     - POSTGRES_DB=jiraservicedeskdb
  desk:
    container_name: jira-servicedesk_prod_desk
    image: cptactionhank/atlassian-jira-service-desk:latest
    depends_on:
      - db
    networks:
      - web
      - servicedesk
    volumes:
      - /opt/docker/04-jira-servicedesk/servicedesk/HOME:/var/atlassian/jira
      - /opt/docker/04-jira-servicedesk/servicedesk/OPT:/opt/atlassian/jira
    environment:
      - CATALINA_OPTS=-Xms786m -Xmx1g
    labels:
      - "traefik.docker.network=web"
      - "traefik.enable=true"
      - "traefik.frontend.rule=Host:servicedesk.domain.com"
      - "traefik.port=8080"
    ports:
      - "8080"

networks:
  web:
     external: true
  servicedesk:

Implement this:
cptactionhank/docker-atlassian-confluence#19

and create acceptance tests for these environment variables

I'd like to install Service Desk, but my understanding was that Jira Core is a pre-req - does this image include both? Thanks.

First off: You're a hero to the community - thanks for your work on these Atlassian containers.

Second: Sadly, to actually upgrade these, as you know, you've got to do it The Hard Way™. I've found that simply upgrading the containers won't migrate the DB since Atlassian isn't that forward thinking yet. I'm not suggesting you do any work to provide that, but I would like to propose something super simple that would help us out.

This line right here, I want the second volume gone for good:

VOLUME ["/var/atlassian/jira", "/opt/atlassian/jira/logs"]

The upgrade binary Atlassian provides requires a complete wipe of the /opt/atlassian directory. It fails when it can't wipe /opt/atlassian, which it can't because it's mounted - rightfully returning a device or resource busy error. Because there's no way to remove this volume during docker run, I have to rebuild this image for every update and exclude that second opt logs volume to actually upgrade jira, or I have to do a dance and move the install directory around, upgrade it, change the JRE_HOME env var, and move everything back (which is a pain).

I'm all about mounting the logs dir, but could we have that be something users need to do during run time? Because your readme told me to, I do it manually anyways in rancher and when running docker run, so I doubt the need to include it in the image is too important. Note that the /var mount can totally stay, it doesn't cause any issues and should probably be forced to prevent data loss anyways.

Additional Context: When upgrading jira "the right way" it requires me to run another container with /bin/bash as the entrypoint and doing the jira upgrade process manually. JIRA has to shut down to upgrade so we can't do it in the already running container as the root pid is jira of course. This proposal would apply to all of your jira containers naturally as the upgrade process is almost identical for all of them.

Thoughts?

Performed an upgrade this morning in my docker and it seems to have updated my DB to a higher version than JIRA and it won't start. I tried to add the flag to downgrade the DB but that didn't work. Any idea why JIRA application didn't upgrade to the latest version?

It would be nice if you can add the JDBC MySQL driver to the image.

I am running this as a service in docker swarm, using docker-flow-proxy to route based on host name. I publish the Jira service on port 8080 and route requests based on 'myhostname.com' on 443 to it, using docker-flow-proxy serviceDomain labels. SSL cert is added as a docker secret, and is picked up fine. It all mostly works - the Jira web app runs and I've gone through the database configuration successfully, but I am getting occasional errors and warnings in Jira UI like the following:

The Tomcat server.xml has an incorrect configuration:
scheme should be https
proxyName should be 'myhostname.com'
proxyPort should be '443'

Dashboard Diagnostics: Mismatched URL Scheme
JIRA is reporting that it is using the URL scheme 'http', which does not match the scheme used to run these diagnostics, 'https'. This is known to cause JIRA to construct URLs using an incorrect hostname, which will result in errors in the dashboard, among other issues.

The most common cause of this is the use of a reverse-proxy HTTP(S) server (often Apache or IIS) in front of the application server running JIRA. While this configuration is supported, some additional setup might be necessary in order to ensure that JIRA detects the correct scheme.

com.atlassian.gadgets.dashboard.internal.diagnostics.UrlSchemeMismatchException: Detected URL scheme, 'http', does not match expected scheme 'https' at com.atlassian.gadgets.dashboard.internal.diagnostics.Diagnostics.checkExpectedScheme(Diagnostics.java:52)

I've looked all throughout the container and can't find tomcat server.xml to edit.
I think this issues is similar to what they describe here: https://confluence.atlassian.com/adminjiraserver073/integrating-jira-with-apache-using-ssl-861253896.html

Please help in how to configure properly.