blog
Table des matières
- 2026:
- 2025:
12 billet(s) pour novembre 2026
| Notes conversion JSON YAML | 2026/11/13 11:16 | Jean-Baptiste |
| Git commit perdu | 2026/11/12 18:16 | Jean-Baptiste |
| Notes mojo lang | 2026/11/11 20:34 | Jean-Baptiste |
| Notes rust lang compilation | 2026/11/11 18:35 | Jean-Baptiste |
| Mémoire VSIZE VMSIZE SEGV lang C | 2026/11/11 15:59 | Jean-Baptiste |
| Ansible-navigator utilisation de ansible-vault | 2026/11/06 11:33 | Jean-Baptiste |
| Err Ansible - Module result deserialization failed No start of json char found | 2026/11/06 09:09 | Jean-Baptiste |
| Script Python conversion JSON vers CSV | 2026/11/06 08:14 | Jean-Baptiste |
| Filter Incoming IPv4 Packets Containing IP Options - cve-2026-98432 mitigation - Kernel TCP Use-After-Free | 2026/11/04 21:04 | Jean-Baptiste |
| Notes ZFS | 2026/11/03 18:04 | Jean-Baptiste |
| Diff image container | 2026/11/03 16:30 | Jean-Baptiste |
| Notes processus multi-thread | 2026/11/03 10:59 | Jean-Baptiste |
Notes PID1 conteneurs
Généralités
Voir ;
Voir aussi :
Design - supervision system vs service manager vs system manager - “hard” and “soft” dependencies.
- init system and service manager https://chimera-linux.org/docs/faq#what-is-the-projects-take-on-systemd
Init process :
Init process pour les conteners :
L'entrypoint devrait être un init tel que “catatonit”
Something like dumb-init or tini can be used if you have a process that spawns new processes and you don't have good signal handlers implemented to catch child signals and stop your child if your process should be stopped etc. If your process doesn't spawn new processes (e.g. Node.js), then this may not be necessary. I guess that MongoDB, PostgreSQL, ... which may run child processes have good signal handlers implemented. Otherwise there would have been zombie processes and someone would have filed an issue to fix this. Only problem may be the official language images, like node, ruby, golang. They don't have dumb-init/tini in it as you normally don't need them. But it's up to the developer which may implement bad child execution code to either fix the signal handlers or use helper as PID 1.
Source : https://stackoverflow.com/questions/37374310/how-critical-is-dumb-init-for-docker
Sans gestion de services
Voir :
Voir :
- tini
- dumb-init
- catatonit (recommandé), utilisé par Podman - inspiré de tini et de dumb-init
- pid1 (paquet pid1) https://github.com/fpco/pid1
Avec gestion de services
Voir :
- runit - fonctionnalités de base incluse dans Busybox - https://wiki.archlinux.org/title/Runit
- S6
- SystemD
Pas classé
Voir :
Ansible AWX reflexion inventaire groups vars host vars
Voir :
Problématique :
Autres PB :
Voir aussi : Ansible variable precedence
Notes namespaces unshare mount bind shared
Voir :
Autres
findmnt -o TARGET,PROPAGATION /opt cat /proc/1/mountinfo
Pb
Err WARN[0001] "/" is not a shared mount, this could cause issues or missing mounts with rootless containers
$ podman pull docker.io/hadolint/hadolint WARN[0001] "/" is not a shared mount, this could cause issues or missing mounts with rootless containers
Solution
sudo mount --make-shared /
Gestion des droits d'accès
Voir :
- RBAC
- MAC
- Syscall / seccomp
- Traditional POSIX permissions
Architecture et code - bonnes pratiques - design pattern
Voir :
Voir aussi :
- Bonnes pratiques Ansible
- Définitions Reproductibilité
- Idempotence - réentrance
- Rootless
- (Serverless) Stateless
Méthode :
- Principe de substitution de Liskov
blog.txt · Dernière modification : de 127.0.0.1
