blog
Table des matières
- 2026:
- 2025:
4 billet(s) pour juillet 2026
| Procédure simple augmentation de la SWAP | 2026/07/17 15:49 | Jean-Baptiste |
| Exemple git clone avec Ansible | 2026/07/16 14:47 | Jean-Baptiste |
| Windows exe - Comparaison de fichiers binaires | 2026/07/16 10:25 | Jean-Baptiste |
| Pb git | 2026/07/01 17:36 | Jean-Baptiste |
Pb Docker Podman
Err cannot set user namespace
$ podman ps cannot set user namespace
Solution
mv /tmp/podman-run-1000 /tmp/podman-run-1000-bak
Pb Docker - device is busy - error response from daemon driver devicemapper failed to remove root filesystem
Source : https://github.com/moby/moby/issues/27381
Pb
# docker rm -f c67056cc52ec Error response from daemon: driver "devicemapper" failed to remove root filesystem for c67056cc52ec0053f08e3bb847ac9c5ec0617bfe99056e0a3371410c80ac9921: failed to remove device 986d057a397700ab66df675365e53c2e8e6b129cc743bbc3bb6e9cc92510e 58e: Device is Busy # rm -rf /var/lib/docker/devicemapper/*/*e58e* rm: impossible de supprimer « /var/lib/docker/devicemapper/mnt/986d057a397700ab66df675365e53c2e8e6b129cc743bbc3bb6e9cc92510e58e »: Périphérique ou ressource occupé
Solution
# find /proc/*/mounts | xargs grep 986d057a397700ab66df675365e53c2e8e6b129cc743bbc3bb6e9cc92510e58e grep: /proc/10975/mounts: Aucun fichier ou dossier de ce type /proc/14426/mounts:/dev/mapper/docker-254:2-183267-986d057a397700ab66df675365e53c2e8e6b129cc743bbc3bb6e9cc92510e58e /var/lib/docker/devicemapper/mnt/986d057a397700ab66df675365e53c2e8e6b129cc743bbc3bb6e9cc92510e58e ext4 rw,relatime,stripe=16,data=ordered 0 0 # ps -p 14426 PID TTY TIME CMD 14426 ? 00:00:00 cupsd # kill 14426 # docker rm c67056cc52ec
Notes
LANG=C dmsetup remove docker-254:2-183267-986d057a397700ab66df675365e53c2e8e6b129cc743bbc3bb6e9cc92510e58e device-mapper: remove ioctl on docker-254:2-183267-986d057a397700ab66df675365e53c2e8e6b129cc743bbc3bb6e9cc92510e58e failed: Device or resource busy dmsetup info -c docker-254:2-183267-986d057a397700ab66df675365e53c2e8e6b129cc743bbc3bb6e9cc92510e58e
La technique suivante n'a pas fonctionné https://askubuntu.com/questions/429612/device-mapper-remove-ioctl-on-luks-xxxx-failed-device-or-resource-busy
$ sudo dmsetup ls luks-xxxxx (252:1) $ sudo lsof | grep 252,1 $ kill -9 1523
Pb DNS resolution - systemd-resolved - timeout short name
$ host www.acme.fr www.acme.fr has address 192.168.1.100
$ time host plop ;; connection timed out; no servers could be reached real 0m10.033s user 0m0.009s sys 0m0.005s
$ systemd-resolve www.acme.fr
www.acme.fr: 192.168.1.100
(www.acme.fr)
-- Information acquired via protocol DNS in 1.7ms.
-- Data is authenticated: no
$ systemd-resolve plop plop: resolve call failed: All attempts to contact name servers or networks failed
Solution
Désactiver LLMNR
/etc/systemd/resolved.conf.d/dns_servers.conf
[Resolve] LLMNR=no
Autres
journalctl -u systemd-resolved.service -f
Cloud - Terrafom / OpenTofu - s3 backend
tf-lock-s3.s
#!/bin/bash # Source : https://github.com/hashicorp/terraform/issues/12877 PROJECT_NAME="${PWD##*/}" # use current dir name AWS_REGION="eu-west-1" ACCOUNT_ID="$(aws sts get-caller-identity --query Account --output text)" aws s3api create-bucket \ --region "${AWS_REGION}" \ --create-bucket-configuration LocationConstraint="${AWS_REGION}" \ --bucket "terraform-tfstate-${ACCOUNT_ID}" aws dynamodb create-table \ --region "${AWS_REGION}" \ --table-name terraform_locks \ --attribute-definitions AttributeName=LockID,AttributeType=S \ --key-schema AttributeName=LockID,KeyType=HASH \ --provisioned-throughput ReadCapacityUnits=1,WriteCapacityUnits=1 cat <<EOF > ./backend_config.tf terraform { backend "s3" { bucket = "terraform-tfstate-${ACCOUNT_ID}" key = "${PROJECT_NAME}" region = "${AWS_REGION}" #lock_table = "terraform_locks" dynamodb_table = "terraform_locks" } } EOF
Pb disque invisible sur HP Proliant disque invisible lors de l'install système RedHat7
Source : Are cciss controllers supported in Red Hat Enterprise Linux 7?
Contrôleur RAID : HP Smart Array E200i controller
Pour que le disque soit vu au boot lors de l'install OS.
Argument à passer au noyaux au boot :
hpsa.hpsa_allow_any=1
blog.txt · Dernière modification : de 127.0.0.1