Docker on Almalinux 10 tuto

Author: dazoulay-simplicite

docs/docs/operation/docker-tutorial.mdx

@@ -6,7 +6,7 @@ title: Docker tutorial
 Deploying Simplicité with Docker images tutorial
 ================================================
 
-For this tutorial we use an out-of-the-box **AlmaLinux/RockyLinux** (or legacy CentOS 7 or Debian) host but this can be transposed to any other host OS.
+For this tutorial we use an out-of-the-box **AlmaLinux 8, 9 or 10** (or legacy CentOS 7 or Debian) host but this can be transposed to any other host OS.
 
 By following the steps below you should have an easily-maintainable **production-grade** deployment of Simplicité up and running **in a few minutes**.
 
@@ -21,7 +21,7 @@ import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
 <Tabs>
-<TabItem value="almalinux" label="AlmaLinux/RockyLinux/CentOS 8+">
+<TabItem value="almalinux" label="AlmaLinux 8, 9 or 10">
 ```shell
 sudo dnf -y update && sudo dnf clean all
 sudo reboot
@@ -49,7 +49,7 @@ filters the access to your host.
 Install and enable firewall :
 
 <Tabs>
-<TabItem value="almalinux" label="AlmaLinux/RockyLinux/CentOS 8+">
+<TabItem value="almalinux" label="AlmaLinux 8, 9 or 10">
 ```shell
 sudo dnf -y install firewalld && sudo dnf clean all
 sudo systemctl enable firewalld
@@ -87,7 +87,7 @@ sudo firewall-cmd --list-all
 This step is not required but provides various useful tools and aliases on your host.
 
 <Tabs>
-<TabItem value="almalinux" label="AlmaLinux/RockyLinux/CentOS 8+">
+<TabItem value="almalinux" label="AlmaLinux 8, 9 or 10">
 ```shell
 sudo dnf -y install vim-enhanced git wget curl zip unzip && sudo dnf clean all
 sudo dnf -y install epel-release && sudo dnf -y install certbot htop && sudo dnf clean all
@@ -104,7 +104,7 @@ sudo yum -y install epel-release && sudo yum -y install certbot htop && sudo yum
 Add these useful aliases to `~/.bashrc`:
 
 <Tabs>
-<TabItem value="almalinux" label="AlmaLinux/RockyLinux/CentOS 8+">
+<TabItem value="almalinux" label="AlmaLinux 8, 9 or 10">
 ```shell
 cat << EOF >> .bashrc
 alias vi=vim
@@ -147,7 +147,7 @@ EOF
 This step is not required if you don't plan to connect to the deployed databases from your host.
 
 <Tabs>
-<TabItem value="almalinux" label="AlmaLinux/RockyLinux/CentOS 8+">
+<TabItem value="almalinux" label="AlmaLinux 8, 9 or 10">
 ```shell
 sudo dnf -y install mariadb postgresql && sudo dnf clean all
 ```
@@ -167,7 +167,27 @@ sudo apt install mariadb-client postgresql-client
 ### Docker
 
 <Tabs>
-<TabItem value="almalinux" label="AlmaLinux/RockyLinux/CentOS 8+">
+<TabItem value="almalinux10" label="AlmaLinux 10">
+
+:::note
+
+Here we install the distribution's Podman
+
+:::
+
+```shell
+sudo dnf -y install podman-docker.noarch
+sudo docker --version
+```
+</TabItem>
+<TabItem value="almalinux9" label="AlmaLinux 8 or 9">
+
+:::note
+
+Here we install Docker CE (Community edition)
+
+:::
+
 ```shell
 sudo dnf -y install 'dnf-command(config-manager)'
 sudo dnf config-manager --add-repo=https://download.docker.com/linux/centos/docker-ce.repo
@@ -178,6 +198,13 @@ sudo systemctl start docker
 ```
 </TabItem>
 <TabItem value="centos7" label="CentOS 7">
+
+:::note
+
+Here we install the distribution's Docker
+
+:::
+
 ```shell
 sudo yum -y install docker && sudo yum clean all
 sudo systemctl enable docker
@@ -196,10 +223,13 @@ sudo systemctl status docker
 </TabItem>
 </Tabs>
 
-> **Note**:
-> By default Docker is allowed to change the firewall rules to open exposed ports.
-> To disable this default behavior you need to edit `/usr/lib/systemd/system/docker.service` cartridge file
-> and add `--iptables=false` (or similar if using `nftables`) to the `ExecStart` command.
+:::tip
+
+By default Docker is allowed to change the firewall rules to open exposed ports.
+To disable this behavior you need to edit `/usr/lib/systemd/system/docker.service` cartridge file
+And add `--iptables=false` (or similar if using `nftables`) to the `ExecStart` command.
+
+:::
 
 Sign-in to **our private Docker registry**:
 
@@ -221,7 +251,12 @@ Where `<tag>` is one of the available tags. E.g. `6-latest` = `6` or `5-latest`
 ### Docker compose
 
 <Tabs>
-<TabItem value="almalinux" label="AlmaLinux/RockyLinux/CentOS 8+ and Debian">
+<TabItem value="almalinux10" label="AlmaLinux 10">
+```shell
+sudo dnf -y install podman-compose.noarch
+```
+</TabItem>
+<TabItem value="almalinux9" label="AlmaLinux 8 or 9 and Debian">
 The compose plugin is installed by default.
 </TabItem>
 <TabItem value="centos7" label="CentOS 7">

docs/docs/operation/tomcat-operation.md

@@ -29,8 +29,10 @@ When required the involved services may need to be stopped in the following orde
 
 Then clean up the Tomcat work folders (and optionally the technical logs folder):
 
-	rm -fr $TOMCAT_ROOT/work/Catalina $TOMCAT_ROOT/conf/Catalina
-	rm -fr $TOMCAT_ROOT/logs/*
+```shell
+rm -fr $TOMCAT_ROOT/work/Catalina $TOMCAT_ROOT/conf/Catalina
+rm -fr $TOMCAT_ROOT/logs/*
+```
 
 Then the services are to be restarted in the following order:
 
@@ -82,10 +84,10 @@ For each logging event, an event **code** is associated, and depending on the co
 
 - The `DEBUG` log level is convenient for investigating an issue but **must not** be set by default.
 - The applicative `ERROR` logs (containing the `SIMPLICITE` keyword) usually correspond to normal application
-errors (the only error logs that requires investigation are the one that correspond to a database problem)
+  errors (the only error logs that requires investigation are the one that correspond to a database problem)
 - The other error logs needs further investigation in any case.
 - Any log at level `FATAL` generally requires services restart with prior technical investigation
-(typically if the error correspond to a memory or file system issue requires actions at OS level)
+  (typically if the error correspond to a memory or file system issue requires actions at OS level)
 
 Housekeeping
 ------------
@@ -161,8 +163,8 @@ For a given application a comprehensive save consist in:
 
 - Saving the database content using an usual database dump tool: `mysqldump`for MySQL or `pgdump`for postgreSQL
 - Saving the documents data directory content located in `$TOMCAT_ROOT/data/simplicite/<my application>/dbdoc`
-  (classical packaging) or `$TOMCAT_ROOT/webapps/ROOT/WEB-INF/dbdoc` (instances packaging) or in a custom location depending on your installation)
-using an usual archive tool: `zip` or `tar`
+  (classical packaging) or `$TOMCAT_ROOT/webapps/ROOT/WEB-INF/dbdoc` (instances packaging) or in a custom location depending on your installation
+  using an usual archive tool: `zip` or `tar`
 
 These two operations needs to be done exactly **at the same time** to avoid any data inconsistencies.
 
@@ -193,7 +195,7 @@ The typical output for the ping is:
 
 The typical output for the health check (in JSON format) is:
 
-```json
+```text
 [Platform]
 Status=OK
 Version=<version, e.g. 5.2.19>
@@ -270,7 +272,8 @@ Date=2022-10-17 12:12:31
 ElapsedTime=230
 ```
 
-If both page/service does not return response or returns a HTTP status different from `200` or if the response value for `status` is not `OK`, something needs to be investigated/fixed.
+If both page/service does not return response or returns a HTTP status different from `200` or if the response value for `status` is not `OK`,
+something needs to be investigated/fixed.
 
 System updates
 --------------
@@ -281,15 +284,21 @@ System updates **must** be applied regularly, especially in case of critical sec
 
 On Linux CentOS, you can check if there are pending system upgrades packages by:
 
-	sudo dnfcheck-update
+```shell
+sudo dnfcheck-update
+```
 
 You can then apply the updates by:
 
-	sudo dnf update
+```shell
+sudo dnf update
+```
 
 You should then clean up update packages by:
 
-	sudo dnf clean all
+```shell
+sudo dnf clean all
+```
 
 If there is an **JVM** update you must stop the running Tomcat instances prior to the update and restart them after the update.
 
@@ -299,8 +308,10 @@ If there is a **kernel** update you must reboot the server after the update.
 
 To clean up old kernels you can do:
 
-	sudo dnf install yum-utils
-	sudo package-cleanup --oldkernels --count=2
+```shell
+sudo dnf install yum-utils
+sudo package-cleanup --oldkernels --count=2
+```
 
 Tomcat updates
 --------------
@@ -312,9 +323,11 @@ The Tomcat server **must** be updated regularly, depending on the way it has bee
 Platform updates
 ----------------
 
-> **Note**: this chapter is not applicable when using our Docker images. When using such images the Simplicité platform is always up-to-date in the latest images.
+> **Note**: this chapter is not applicable when using our Docker images. When using such images the Simplicité
+> platform is always up-to-date in the latest images.
 
-The Simplicité&reg; platform **must** be updated regularly, at least on its maintenance branch (see [versions](/versions/versioning.md)), depending on the way it has been installed the process may vary.
+The Simplicité&reg; platform **must** be updated regularly, at least on its maintenance branch (see [versions](/versions/versioning.md)),
+depending on the way it has been installed the process may vary.
 
 Troubleshooting
 ---------------