RHEL9 ALMA9 is deployed with the portainer docker container management panel

Current update 202312.14

Continuously updating.

1. Install alma9

ALMA's official website, I'm using a miniiso image.

2. System configuration.

Enable SSH login.

See Red Hat official help, root SSH is not allowed to log in by default.

[root@admin ~]# echo 'permitrootlogin yes' >>/etc/ssh/sshd_config.d/01-permitrootlogin.conf[root@admin ~]# systemctl restart sshd.service

3. Install docker

yum install -y yum-utils official source yum-config-manager --add-repo Alibaba Cloud acceleration source yum-config-manager --add-repo install docker-ce docker-ce-cli containerdio

Image source.

/etc/docker/daemon.json

systemctl enable --now docker

Create a storage volume.

docker volume create portainer_data

docker run -d -p 8000:8000 -p 9443:9443 --name portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:latest

Once running, log in https: ip:9443

Create your first admin user.

Log in to Local to get started.

Main interface.

Container management.

Persistent volume management.

Image source configuration.

1. Create a container.

Create a container.

Parameters such as container name and port mapping.

Advanced options. Persist Volume Variable Restart Policy.

Container restart will lose all the data generated during operation, so you need to set container data persistence, such as the etc nginx directory configuration file of the nginx container and the usr share nginx web directory.

Some containers require variables, such as mysql8., to be configured for deployment2. The mysql root password variable is required, otherwise the startup fails.

The reboot policy is usually configured to Always Always to enable boot auto-start.

2. Recreate the container.

High-risk operations. If the container is abnormal, you can recreate the container, and all container data will be lost except for persistent data.

This option can also be used to update containers, for containers that use the latest label.

3. Edit the container.

High-risk operations. You can modify container parameters, such as mapping ports and persistence, and all container data is lost except for persistent data.

4. Containers are opened, closed, restarted, suspended, resumed, and deleted.

5. Mirroring. Manage the mirrors that have been **.

6. Persistence.

Manage persistent volumes.

7. Deploy applications.

1、mysql8.2

Required variable: mysql root password

Map port 3306

Automatic persistence.

Note that due to mysql82. The default encryption method has been modified, and the client may not be able to connect!

root connection.

If you use dbe**er, the default connection will be reportedpublic key retrieval is not allowed, you need to set the allowpublickeyretrieval in the driver property to true, and then you can use the root connection.

Regular user connection.

Currently, most applications do not support mysql82. If you encounter mysql and cannot connect, you can create a new common user and change the user to the old password encryption mode.

alter user 'typecho'@'%' identified with mysql_native_password by 'passwd';

Map port 443 80

Mapping directories. 1) nginx configuration directory, i.e. nginx's etc nginx is mapped to nginxconf volume.

2) Nginx web directory, i.e. nginx's usr share nginx is mapped to nginx-www volumes.

When you modify the configuration or place a web page, you can modify it through the mount directory of the volume.

3、php-fpm

Map port 9000

Mapping directory The mapping directory is the nginx web directory, that is, the usr share nginx of nginx is mapped to the nginx-www volume, and the usr share nginx of php-fpm is also mapped to the nginx-www volume, so that php-fpm can read the files of the nginx web directory.

4、librespeed

Map port 80

Automatic persistence.

5、typecho

Map port 80

Automatic persistence.

6、uptime-kuma

Map port 3001

Automatic persistence.

8. Summary. It's so powerful!