docker部署jira(8.0.0)和confluence(6.14.1)

yum update -y
reboot

wget https://dev.mysql.com/get/mysql57-community-release-el7-11.noarch.rpm
rpm -Uvh mysql57-community-release-el7-11.noarch.rpm

[root@jt-jira ~]# yum list mysql-community-server --showduplicates | sort -r
 * updates: mirrors.aliyun.com
mysql-community-server.x86_64           5.7.9-1.el7            mysql57-community
mysql-community-server.x86_64           5.7.25-1.el7           mysql57-community
mysql-community-server.x86_64           5.7.24-1.el7           mysql57-community
mysql-community-server.x86_64           5.7.23-1.el7           mysql57-community
mysql-community-server.x86_64           5.7.22-1.el7           mysql57-community
mysql-community-server.x86_64           5.7.21-1.el7           mysql57-community
mysql-community-server.x86_64           5.7.20-1.el7           mysql57-community
mysql-community-server.x86_64           5.7.19-1.el7           mysql57-community
mysql-community-server.x86_64           5.7.18-1.el7           mysql57-community
mysql-community-server.x86_64           5.7.17-1.el7           mysql57-community
mysql-community-server.x86_64           5.7.16-1.el7           mysql57-community
mysql-community-server.x86_64           5.7.15-1.el7           mysql57-community
mysql-community-server.x86_64           5.7.14-1.el7           mysql57-community
mysql-community-server.x86_64           5.7.13-1.el7           mysql57-community
mysql-community-server.x86_64           5.7.12-1.el7           mysql57-community
mysql-community-server.x86_64           5.7.11-1.el7           mysql57-community
mysql-community-server.x86_64           5.7.10-1.el7           mysql57-community

yum list mysql-community-server

cat>/etc/my.cnf.d/client.cnf<<EOF
[client]
default-character-set=utf8
EOF

cat>/etc/my.cnf.d/mysql-clients.cnf<<EOF
[mysql]
default-character-set=utf8
EOF

cat>>/etc/my.cnf<<EOF
default-storage-engine=INNODB     # 将默认存储引擎设置为InnoDB
character_set_server=utf8mb4      # 指定数据库服务器使用的字符集
innodb_default_row_format=DYNAMIC # 将默认行格式设置为  DYNAMIC
innodb_large_prefix=ON            # 启用大前缀
innodb_file_format=Barracuda      # 将InnoDB文件格式设置为Barracuda
innodb_log_file_size=2G           # innodb_log_file_size至少为2G
EOF

systemctl enable --now mysqld

[root@jt-jira ~]# grep 'temporary password' /var/log/mysqld.log 
2019-02-18T09:07:42.064502Z 1 [Note] A temporary password is generated for root@localhost: E#xxxxxxx9Od

[root@jt-jira ~]# mysql_secure_installation 

Securing the MySQL server deployment.

Enter password for user root: <–初次运行输入log里的root密码

The existing password for the user account root has expired. Please set a new password.

New password: <– 设置root用户的密码,复杂度不够可能会被再次要求输入

Re-enter new password: <– 再输入一次你设置的密码
The 'validate_password' plugin is installed on the server.
The subsequent steps will run with the existing configuration
of the plugin.
Using existing password for root.

Estimated strength of the password: 100  
Change the password for root ? ((Press y|Y for Yes, any other key for No) : No <– 输入No,前面设置过root密码了

 ... skipping.
By default, a MySQL installation has an anonymous user,
allowing anyone to log into MySQL without having to have
a user account created for them. This is intended only for
testing, and to make the installation go a bit smoother.
You should remove them before moving into a production
environment.

Remove anonymous users? (Press y|Y for Yes, any other key for No) : y <– 是否删除匿名用户，输入y回车
Success.


Normally, root should only be allowed to connect from
'localhost'. This ensures that someone cannot guess at
the root password from the network.

Disallow root login remotely? (Press y|Y for Yes, any other key for No) : y <–是否禁止root远程登录,看需求,如果开发用得多就不禁止,这里动得少我是直接禁止掉的
Success.

By default, MySQL comes with a database named 'test' that
anyone can access. This is also intended only for testing,
and should be removed before moving into a production
environment.


Remove test database and access to it? (Press y|Y for Yes, any other key for No) : y  <– 是否删除test数据库，输入y回车
 - Dropping test database...
Success.

 - Removing privileges on test database...
Success.

Reloading the privilege tables will ensure that all changes
made so far will take effect immediately.

Reload privilege tables now? (Press y|Y for Yes, any other key for No) : y 是否重新加载权限表，输入y回车
Success.

All done!

sed -ri '/temporary password/d' /var/log/mysqld.log

mysql -uroot -p

mysql> create database jira default character set utf8 collate utf8_bin;
mysql> grant all on jira.* to 'jira'@'%' identified by 'v8xxxxxxx1';

sudo curl -L "https://github.com/docker/compose/releases/download/1.23.2/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
chmod +x /usr/local/bin/docker-compose

cp /usr/share/bash-completion/completions/docker /etc/bash_completion.d/
systemctl enable --now docker

+ '[' -r /opt/atlassian/jira/bin/setenv.sh ']'
+ . /opt/atlassian/jira/bin/setenv.sh


$ cat /opt/atlassian/jira/bin/setenv.sh
...
JAVA_OPTS="-Xms${JVM_MINIMUM_MEMORY} -Xmx${JVM_MAXIMUM_MEMORY} ${JVM_CODE_CACHE_ARGS} ${JAVA_OPTS} ${JVM_REQUIRED_ARGS} ${DISABLE_NOTIFICATIONS} ${JVM_SUPPORT_RECOMMENDED_ARGS} ${JVM_EXTRA_ARGS} ${JIRA_HOME_MINUSD} ${START_JIRA_JAVA_OPTS}"
...
export JAVA_OPTS

[root@jt-jira jira]# docker exec jira sh -c 'echo $LANG'
C.UTF-8

version: '3.7'
services:
  jira:
    image: zhangguanzhang/atlassian-jira-software:8.0.0
    container_name: jira
    hostname: jira
    init: true
    volumes:
      - JIRA_HOME_data:/var/atlassian/jira
      - JIRA_log_data:/opt/atlassian/jira/logs
      - /etc/localtime:/etc/localtime:ro
    ports:
      - '8080:8080'
    logging:
      driver: json-file
      options:
        max-file: '3'
        max-size: 100m
volumes:
  JIRA_HOME_data: {}
  JIRA_log_data: {}

cat>>/etc/my.cnf<<EOF
character-set-server=utf8     
collation-server=utf8_bin      # 将默认字符集指定为UTF-8
default-storage-engine=INNODB  # 将默认存储引擎设置为InnoDB
max_allowed_packet=256M        # max_allowed_packet至少为256M
innodb_log_file_size=2GB       # innodb_log_file_size 至少为2GB
transaction-isolation=READ-COMMITTED  # 确保数据库的全局事务隔离级别已设置为READ-COMMITTED
binlog_format=row              # 检查二进制日志记录格式是否配置为使用“基于行”的二进制日志记录
EOF