Forem: Jean Pierre

My private cloud in my Homelab

Jean Pierre — Sun, 21 Sep 2025 03:08:13 +0000

Sobre mim

Olá, sou Jean Pierre e estou registrando aqui a minha trajetória para me tornar um DevOps/SRE.

Meu objetivo é montar um ambiente de laboratorio em onpremisses para estudar as tecnologias de Cloud, ex: Kubernetes(k8s), pipeline CI/CD, Observabilidade (monitoramento e alertas), repositório de código, repositório de imagens, ferramentas de deploy, loadbalance (nginx), aplicações web em Python (Django, FastAPI e Flask) e NodeJS/TypeScript (NestJS, VueJS, React), banco de dados (MongoDB e MariaDB).

Infraestrutura

M80q Desktop (ThinkCentre) - Type 11DQ

Intel(R) Core(TM) i5-10500T CPU @ 2.30GHz
32GB (2x16GB) SODIMM DDR4 Synchronous 2667 MHz (0.4 ns)
CometLake-S GT2 [UHD Graphics 630]
512GB SSD NVMe PCIe 3.0x4
2TB HDD

Hardware

Componentes

Por dentro

Proxmox

Linux proxmox 6.8.12-9-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.12-9 x86_64 GNU/Linux

Next step: Building a Cluster with Docker Swarm

Building a Cluster with Docker Swarm

Jean Pierre — Sun, 21 Sep 2025 03:06:21 +0000

Summary

Previous step: My private cloud in my Homelab

Header:

1. My private cloud in my Homelab

Next step: Building a Cluster with Docker Swarm

in progress...

Next step: Building a Cluster with Docker Swarm

Update de BIOS no Linux

Jean Pierre — Mon, 30 Sep 2024 17:39:44 +0000

TLDR

fwupdmgr refresh --force

then

fwupdmgr get-updates

then

fwupdmgr update

Criptografando um SSD/HDD manualmente no Linux com o CryptSetup (LUKS)

Jean Pierre — Sat, 08 Jun 2024 17:13:13 +0000

Criptografando um SSD/HDD manualmente no Linux com o CryptSetup (LUKS)

disclaymer (opcoes e modos de criptografar)

1. Identificar o disco

op1 - pelo tamanho do disco
op2 - caso tenha 2 discos iguais, usar o mount ou apenas desconectar um dos discos e ver qual é o novo

2. Criar partição a ser criptografada

2.1. precisei apagar as particoes existentes.

box@box:~$ sudo gdisk /dev/sdc
GPT fdisk (gdisk) version 1.0.6

The protective MBR's 0xEE partition is oversized! Auto-repairing.

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help): p
Disk /dev/sdc: 3907029168 sectors, 1.8 TiB
Model: Generic         
Sector size (logical/physical): 512/4096 bytes
Disk identifier (GUID): 954C8903-2CD3-4EF4-B907-632776F3A1BC
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 2048-sector boundaries
Total free space is 3874242669 sectors (1.8 TiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048          309247   150.0 MiB   EF00  EFI system partition
   2          309248          571391   128.0 MiB   0C01  Microsoft reserved ...
   3      3874785280      3876812799   990.0 MiB   2700  
   4      3876812800      3904253951   13.1 GiB    2700  
   5      3904256000      3907004415   1.3 GiB     2700  

Command (? for help): d
Partition number (1-5): 1

Command (? for help): d
Partition number (2-5): 2

Command (? for help): d
Partition number (3-5): 3

Command (? for help): d
Partition number (4-5): 4

Command (? for help): d
Using 5

2. Criando partição

Command (? for help): c
No partitions

Command (? for help): n
Partition number (1-128, default 1): 
First sector (34-3907029134, default = 2048) or {+-}size{KMGTP}: 
Last sector (2048-3907029134, default = 3907029134) or {+-}size{KMGTP}: 
Current type is 8300 (Linux filesystem)
Hex code or GUID (L to show codes, Enter = 8300): 
Changed type of partition to 'Linux filesystem'

Command (? for help): w

Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!

Do you want to proceed? (Y/N): Y
OK; writing new GUID partition table (GPT) to /dev/sdc.
The operation has completed successfully.

3. Formatando a partição para o formato LUKS

box@box:~$ sudo fdisk -l | grep "sdc"
Disk /dev/sdc: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
/dev/sdc1   2048 3907029134 3907027087  1.8T Linux filesystem
box@box:~$ sudo cryptsetup luksFormat /dev/sdc1
WARNING: Device /dev/sdc1 already contains a 'vfat' superblock signature.

WARNING!
========
This will overwrite data on /dev/sdc1 irrevocably.

Are you sure? (Type 'yes' in capital letters): YES
Enter passphrase for /dev/sdc1: 
Verify passphrase:

4. Decriptografando

box@box:~$ sudo cryptsetup open /dev/sdc1 hd_swap
Enter passphrase for /dev/sdc1:

4.1 Listando partição descriptografada

box@box:~$ sudo fdisk -l | grep hd_swap
Disk /dev/mapper/hd_swap: 1.82 TiB, 2000381091328 bytes, 3906994319 sectors

5. Formatando

box@box:~$ sudo mkfs.ext4 /dev/mapper/hd_swap
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 488374272 4k blocks and 122332032 inodes
Filesystem UUID: 1af577e5-48a0-470d-a510-ddb9bc3c9935
Superblock backups stored on blocks: 
    32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
    4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 
    102400000, 214990848

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done

6. Montando a partição

box@box:~$ mkdir -pv /media/box/hd_swap
mkdir: created directory '/media/box/hd_swap'
box@box:~$ sudo mount /dev/mapper/hd_swap /media/box/hd_swap -v
mount: /dev/mapper/hd_swap mounted on /media/box/hd_swap.

[LINUX] Partição "/boot" cheio

Jean Pierre — Mon, 18 Dec 2023 00:22:42 +0000

Depois de uns meses sempre que atualizamos o sistema com base linux(ubuntu da vida) ele começa a deixar o /boot cheio com arquivos de versões de kernel antigas.

Com o passo a passo abaixo vamos conseguir executar alguns comandos para identificar arquivos antigos e apaga-los facilmente

TDLR

Para REMOVER todos os arquivos inúteis MENOS os arquivos utilizados atualmente:
Comando:

$ sudo rm -v $(ls /boot/*-generic | egrep -v $(uname -r))
$ sudo update-initramfs -v -c -k all
$ sudo update-grub2

Entendendo como identificar para aprender decorar e não precisar mais googar

Para descobrir a versão do kernel atual:
Comando:

$ uname -r

Saída:

5.15.0-91-generic

Para listar todos os arquivos de kernel:
Comando:

$ ls -l /boot/*-generic

Saída:

-rw-r--r-- 1 root root    253465 Jun 17  2021 /boot/config-5.11.0-22-generic
-rw-r--r-- 1 root root    262258 Aug 18 11:34 /boot/config-5.15.0-82-generic
-rw-r--r-- 1 root root    262146 Oct  5 05:10 /boot/config-5.15.0-87-generic
-rw-r--r-- 1 root root    262146 Nov  2 11:04 /boot/config-5.15.0-89-generic
-rw-r--r-- 1 root root    262265 Nov 16 10:58 /boot/config-5.15.0-91-generic
-rw-r--r-- 1 root root    237851 Jun 16  2021 /boot/config-5.4.0-77-generic
-rw-r--r-- 1 root root 129803030 Aug 30 02:52 /boot/initrd.img-5.15.0-82-generic
-rw-r--r-- 1 root root 129802342 Oct 19 14:04 /boot/initrd.img-5.15.0-87-generic
-rw-r--r-- 1 root root 129816017 Nov 21 00:51 /boot/initrd.img-5.15.0-89-generic
-rw-r--r-- 1 root root 129837544 Dec 15 12:25 /boot/initrd.img-5.15.0-91-generic
-rw------- 1 root root   5832311 Jun 17  2021 /boot/System.map-5.11.0-22-generic
-rw------- 1 root root   6240491 Aug 18 11:34 /boot/System.map-5.15.0-82-generic
-rw------- 1 root root   6244586 Oct  5 05:10 /boot/System.map-5.15.0-87-generic
-rw------- 1 root root   6245349 Nov  2 11:04 /boot/System.map-5.15.0-89-generic
-rw------- 1 root root   6242483 Nov 16 10:58 /boot/System.map-5.15.0-91-generic
-rw------- 1 root root   4751546 Jun 16  2021 /boot/System.map-5.4.0-77-generic
-rw------- 1 root root  10118208 Jun 17  2021 /boot/vmlinuz-5.11.0-22-generic
-rw------- 1 root root  11522568 Aug 18 13:03 /boot/vmlinuz-5.15.0-82-generic
-rw------- 1 root root  11523784 Oct  5 05:13 /boot/vmlinuz-5.15.0-87-generic
-rw------- 1 root root  11521320 Nov  2 11:05 /boot/vmlinuz-5.15.0-89-generic
-rw------- 1 root root  11517416 Nov 16 11:01 /boot/vmlinuz-5.15.0-91-generic

Para listar os arquivos de kernel utilizados atualmente:
Comando

$ ls -l /boot/*-generic | egrep $(uname -r)

Saída:

-rw-r--r-- 1 root root    262265 Nov 16 10:58 /boot/config-5.15.0-91-generic
-rw-r--r-- 1 root root 129837544 Dec 15 12:25 /boot/initrd.img-5.15.0-91-generic
-rw------- 1 root root   6242483 Nov 16 10:58 /boot/System.map-5.15.0-91-generic
-rw------- 1 root root  11517416 Nov 16 11:01 /boot/vmlinuz-5.15.0-91-generic

Para listar todos os arquivos de kernel MENOS os arquivos utilizados atualmente:

$ ls -l /boot/*-generic | egrep -v $(uname -r) 
-rw-r--r-- 1 root root    253465 Jun 17  2021 /boot/config-5.11.0-22-generic
-rw-r--r-- 1 root root    262258 Aug 18 11:34 /boot/config-5.15.0-82-generic
-rw-r--r-- 1 root root    262146 Oct  5 05:10 /boot/config-5.15.0-87-generic
-rw-r--r-- 1 root root    262146 Nov  2 11:04 /boot/config-5.15.0-89-generic
-rw-r--r-- 1 root root    237851 Jun 16  2021 /boot/config-5.4.0-77-generic
-rw-r--r-- 1 root root 129803030 Aug 30 02:52 /boot/initrd.img-5.15.0-82-generic
-rw-r--r-- 1 root root 129802342 Oct 19 14:04 /boot/initrd.img-5.15.0-87-generic
-rw-r--r-- 1 root root 129816017 Nov 21 00:51 /boot/initrd.img-5.15.0-89-generic
-rw------- 1 root root   5832311 Jun 17  2021 /boot/System.map-5.11.0-22-generic
-rw------- 1 root root   6240491 Aug 18 11:34 /boot/System.map-5.15.0-82-generic
-rw------- 1 root root   6244586 Oct  5 05:10 /boot/System.map-5.15.0-87-generic
-rw------- 1 root root   6245349 Nov  2 11:04 /boot/System.map-5.15.0-89-generic
-rw------- 1 root root   4751546 Jun 16  2021 /boot/System.map-5.4.0-77-generic
-rw------- 1 root root  10118208 Jun 17  2021 /boot/vmlinuz-5.11.0-22-generic
-rw------- 1 root root  11522568 Aug 18 13:03 /boot/vmlinuz-5.15.0-82-generic
-rw------- 1 root root  11523784 Oct  5 05:13 /boot/vmlinuz-5.15.0-87-generic
-rw------- 1 root root  11521320 Nov  2 11:05 /boot/vmlinuz-5.15.0-89-generic

Para REMOVER todos os arquivos listados MENOS os arquivos utilizados atualmente:
Comando:

$ sudo rm -v $(ls /boot/*-generic | egrep -v $(uname -r))

Saída:

removed '/boot/config-5.11.0-22-generic'
removed '/boot/config-5.15.0-82-generic'
removed '/boot/config-5.15.0-87-generic'
removed '/boot/config-5.15.0-89-generic'
removed '/boot/config-5.4.0-77-generic'
removed '/boot/initrd.img-5.15.0-82-generic'
removed '/boot/initrd.img-5.15.0-87-generic'
removed '/boot/initrd.img-5.15.0-89-generic'
removed '/boot/System.map-5.11.0-22-generic'
removed '/boot/System.map-5.15.0-82-generic'
removed '/boot/System.map-5.15.0-87-generic'
removed '/boot/System.map-5.15.0-89-generic'
removed '/boot/System.map-5.4.0-77-generic'
removed '/boot/vmlinuz-5.11.0-22-generic'
removed '/boot/vmlinuz-5.15.0-82-generic'
removed '/boot/vmlinuz-5.15.0-87-generic'
removed '/boot/vmlinuz-5.15.0-89-generic'

[LINUX] Como alterar o layout do teclado Debian (VM)

Jean Pierre — Wed, 04 Oct 2023 19:50:39 +0000

Toda vez que instalo uma VM debian no meu virtualbox eu me deparo com esse problema
Há uns bons meses eu não precisava instalar, pois utilizava tudo em containers dockers ou LXC, mas desta vez é/foi preciso instalar em uma VM (host).
Assim que feita a instalação, o teclado do VM trocava algumas (muitas) teclas, por exemplo, a "/" do teclado meu teclado fisico era interpretada como "-" na VM e com isso nem pra editar os arquivos eu conseguia!
Logo precisei fazer uma configuração com o dpkg (executar como root #)

# dpkg-reconfigure locales

Escolhi o locale de minha preferência (como o padrão das VMs e servidores são no idioma en-us, o mantive)
O deixei como padrão na tela a seguir

Após aplicar, eu reiniciei o computador

# init 6

Finsh!