💾 Installer Immich

1. Créer le dossier Immich:

mkdir immich

1. Se rendre dans le dossier:

cd immich

1. Récupérez le docker-compose.yml:

wget -O docker-compose.yml https://github.com/immich-app/immich/releases/latest/download/docker-compose.yml

1. Récupérez le .env:

wget -O .env https://github.com/immich-app/immich/releases/latest/download/example.env

1. Il est maintenant temps de lancer l'installation d'Immich:

docker-compose up -d

ou avec docker-compose V2:

docker compose up -d

1. Quand l'installation est terminée, rendez-vous sur le lien suivant avec votre navigateur (en prenant soin de changer "ip" par l'IP locale de votre serveur):

http://ip:2283

Installer immiche Frame dans un sous dossier

mkdir immich-dossier 1

nano compose.yml

1. Stick it in :

name: immichframe-Dossier1
services:
  immichframe:
    container_name: immichframe-dossier1
    image: ghcr.io/immichframe/immichframe:latest
    restart: on-failure
    ports:
      - "8600:8080"
    environment:
      TZ: "Europe/Brussels"
      # Required
      ImmichServerUrl: "http://192.168.1.176:2283"
      ApiKey: "4QUdiSTbT1ZaLu7J0vmLFesAEOBzXvJBj6pe8rfQYig"
      #Security
      AuthenticationSecret: "test"
      # Image
      ImageZoom: "true"  
      Interval: "10"
      TransitionDuration: "2"
      # Filters
      Albums: "09a4a1ee-18f2-4bfa-8094-41e55063c1e7"
      ShowMemories: "false"
      ShowFavorites: "false"
      ImagesFromDays: ""
      ImagesFromDate: ""
      ImagesUntilDate: ""
      # Clock
      ShowClock: "true"
      ClockFormat: "HH:mm"
      # Metadata
      ShowImageDesc: "true"
      ShowImageLocation: "true"
      ShowPhotoDate: "true"
      PhotoDateFormat: "yyyy-MM-dd"
      # Caching
      RenewImagesDuration: "30"
      DownloadImages: "false"
      RefreshAlbumPeopleInterval: "12"
      # UI
      PrimaryColor: "#FF5733"
      BaseFontSize: "17px"
      # Misc
      ImmichFrameAlbumName: ""
      Style: "none"
      Layout: "splitview"

Si plusieur instances créer a chaque fois un nouveau dossier et replacer le fichier docker compose.yml

pvecm expect 1

Guide pratique des règles concernant les bagages pour les vols en 2024 et conseils pour le voyage ! – Dealabs.com

Poster…

Les règles des différentes compagnies aériennes

Avant de prendre votre vol, consultez toujours les directives de la compagnie aérienne spécifique avec laquelle vous voyagez, car ces règles peuvent varier et sont sujettes à des modifications. Les informations ci-après peuvent avoir changé depuis la rédaction de cet article !

Pour la plupart des compagnies, il vaut mieux réserver vos bagages en ligne plutôt qu'au moment de l'enregistrement à l'aéroport, les tarifs peuvent aller du simple au triple...
Le bagage à main doit normalement pouvoir être placé sous le siège situé devant vous, le bagage cabine est rangé dans les espaces de rangement prévus au dessus des sièges.
En général, les poignées et roulettes doivent être inclus dans les dimensions indiquées.

➥ Air France
Bagages en Cabine

• 55 x 35 x 25 cm - jusqu'à 12kg + 1 accessoire 40 x 30 x 15 cm

Bagages en Soute

• 158 cm (longueur + largeur + hauteur) - jusqu'à 23 kg en classe éco (avec frais supplémentaires)

Réservations : wwws.airfrance.fr/

➥ Ryanair
Bagages en Cabine

• Bagage à main : 40 x 20 x 25 cm
• Bagage cabine : 55 x 40 x 20 cm - jusqu'à 10 kg (avec frais supplémentaires)

Bagages en Soute

• Jusqu'à 120 x 120 x 80 cm et 20 kg (avec frais supplémentaires)

Réservations : ryanair.com/fr/fr

➥ EasyJet
Bagages en Cabine

• 1 bagage à main : 45 x 36 x 20 cm - jusqu'à 15 kg
• 1 bagage cabine : 56 x 45 x 25 cm - Aucune limite de poids spécifique (avec frais supplémentaires)

Bagages en Soute

• 275 cm (longueur + largeur + hauteur) - jusqu'à 32 kg (avec frais supplémentaires)

Réservations : easyjet.com/fr

➥ Transavia
Bagages en Cabine

• 1 Bagage à main (40 x 30 x 20 cm) + 1 Bagage cabine (55x 35x 25cm) - jusqu'à 10 kg pour les 2 ensemble

Bagages en Soute

• Poids maximal : jusqu'à 50 kg (avec frais supplémentaires)

Réservations : transavia.com/fr-…il/

➥ Volotea
Bagages en Cabine

• 1 bagage à main : 40 x 30 x 20 cm
• 1 bagage cabine : 55 x 40 x 20 cm - jusqu'à 10 kg bagage à main inclus (avec frais supplémentaires ou membre Megavolotea)

Bagages en Soute

• Poids maximal : jusqu'à 50 kg par passager (avec frais supplémentaires)

Réservations : volotea.com/fr

➥ Vueling
Bagages en Cabine

• 1 bagage à main : 40 x 30 x 20 cm
• 1 bagage cabine : 55 x 40 x 20 cm - jusqu'à 10 kg bagage à main inclus (avec frais supplémentaires)

Bagages en Soute

• 158 cm (longueur + largeur + hauteur) - jusqu'à 30 kg (avec frais supplémentaires)

Réservations : vueling.com/fr

➥ Wizz Air
Bagages en Cabine

• 1 bagage à main : 40 x 30 x 20 cm
• 1 bagage cabine : 55 x 40 x 23 cm (avec frais supplémentaires)

Bagages en Soute

• 149 x 119 x 171 cm - jusqu'à 32 kg (avec frais supplémentaires)

Réservations : wizzair.com/fr-fr

Et sans faire le détail :
➥ Turkish Airlines
➥ British Airways
➥ Emirates
➥ Lufthansa
➥ Iberia
➥ KLM
➥ TAP Air Portugal
➥ Aegean

En cliquant sur le nom de la compagnie, vous accéderez à la page dédiée détaillant les règles en vigueur de la dite compagnie

Que peut-on transporter en cabine ?

Les liquides
Chaque passager peut transporter un sac en plastique 20 x 20 cm fermé, de moins d'un litre, avec des contenants maximum de 100ml pour les liquides, crèmes et pâtes.
Cet aspect est amené à évoluer avec des scanners 3D testés dans certains aéroports, mais pour l'instant il faut toujours se plier à ces obligations...
Certaines dérogations peuvent être faites, pour un bébé ou sur ordonnance par exemple.

Les produits interdits

• Objets coupants, tranchants ou pointus, tels que tournevis, ciseaux, couteau (si la lame dépasse 6 cm)
• Autres objets pouvant blesser, tels que bâton de marche, skate-board
• Armes (y compris jouets ou imitations d'armes)
• Produits inflammables

En cas de doute vous pouvez vérifier article par article les règles en vigueur sur ce site : airbag.dsac.aviation-civile.gouv.fr/AirBag

Les conseils pour préparer sa valise

• Faites une liste : Avant de commencer à faire vos valises, cela vous aidera à éviter d’oublier des éléments importants.

• Roulez vos vêtements au lieu de les plier. Cela permet non seulement d'économiser de l'espace, mais aide également à prévenir les plis.

• Optez pour des vêtements passe-partout : choisissez des vêtements que vous pouvez mélanger et assortir facilement pour varier vos tenues sans surcharger votre valise

• Utilisez des organiseurs de bagage : ils vous aident à maximiser l’espace et à vous y retrouver plus facilement.

• Emballez les objets lourds en bas : cela facilite la gestion de votre valise et évite que les objets plus légers ne soient écrasés.

• Pensez aux accessoires multifonctions : choisissez des accessoires polyvalents tels que des écharpes ou des châles qui peuvent servir de couverture, de foulard ou de protection solaire.

• Préparez votre bagage cabine avec soin : Emportez toujours des vêtements de rechange, des articles de toilette essentiels, une réserve de médicaments et des documents importants dans votre bagage à main, au cas où vos bagages enregistrés seraient perdus.

• Emportez au moins une bouteille vide : vous pourrez trouver une fontaine à eau et la remplir une fois passés les contrôles à l'aéroport, et ainsi boire pendant votre trajet sans passer à la caisse pour une Vittel 50cl à 3€ . Vous pouvez également emballez quelques aliments coupe-faim.

• Utilisez les espaces vides : remplissez les chaussures et autres espaces vides avec de petits objets comme des chaussettes ou des sous-vêtements.

• Emportez une trousse de premiers soins de voyage : incluez des articles comme des pansements, des analgésiques et tout médicament sur ordonnance.

• N'oubliez pas les chargeurs et les adaptateurs : si vous voyagez à l'étranger, vous aurez peut-être besoin d'un adaptateur secteur. N’oubliez pas non plus d’emporter des chargeurs pour tous vos appareils.

• Privilégiez les articles de toilette au format voyage : utilisez de petits contenants pour économiser du poids et de l’espace. Vous pouvez par exemple trouver des petits flacons rechargeables pour les parfums, afin de n'emporter que ce qui vous sera utile pendant la durée de votre séjour.

• Préparez vos documents numériques : conservez les documents de voyage comme les cartes d'embarquement sur votre téléphone pour un accès facile. Gardez des copies numériques de certains documents importants dans des fichiers sécurisés, ça peut servir en cas de problème !

• Achetez des bagages légers : pour réduire le poids et augmenter l’espace pour les objets personnels.

Astuces pour voyager avec un bagage cabine (sac à dos) uniquement :

Mise en place du dossier partagé

Afin que ça soit plus simple pour moi de gérer le tout, j'ai décidé d'utiliser mon NAS (un Synology) en tant que serveur SMB. Si vous préférez utiliser un disque dur externe, faites-le donc, mais pensez donc à le monter depuis le dashboard de Proxmox.

Il faudra créer un utilisateur sur le serveur SMB qui aura uniquement accès au dossier videos et qui aura les droits de lecture, d'écriture, et d'accès aux sous-dossiers. Pour cela, je vous laisse faire les manipulations nécessaires en fonction de votre installation.

Une fois fait, il va falloir qu'on s'assure de bien connecter notre conteneur au serveur distant. Donc, on va commencer par créer un dossier /media/video sur le conteneur LXC.

mkdir /media/video

Puis, on va créer un service qui va monter pour ce dossier. Attention cela dit à le nommer exactement comme cela, sinon ce dernier ne fonctionnera pas un peu plus tard.

nano /etc/systemd/system/media-video.mount

On va mettre le contenu suivant. N'oubliez pas de changer l'IP et le répertoire source dans What= si votre dossier diffère d'un Synology...

[Unit]
  Description=cifs mount script
  Requires=network-online.target
  After=network-online.service

[Mount]
  # REMPLACER <IP> par l'IP de notre NAS (comme 192.168.0.200), ainsi que le
  # dossier cible si ce dernier n'est pas au même endroit.
  What=//<IP>/video
  Where=/media/video
  Options=credentials=/root/.smb,noperm
  Type=cifs

[Install]
  WantedBy=multi-user.target

Enfin, on va créer un fichier dans le dossier /root qui contiendra nos informations de compte pour se connecter au serveur SMB.

nano /root/.smb

username=my_user_dedicated_to_video_folder
password=this_is_my_password

Enfin, on va installer le service CIFS permettant de mettre en lien entre le serveur Synology et notre conteneur LXC:

apt update && apt install cifs-utils

On va pouvoir désormais créer le service.

systemctl enable media-video.mount
systemctl start media-video.mount

Si aucun message d'erreur apparait, regardez le contenu dans le dossier qu'on a monté. Et de plus, dans Jellyfin, vous devriez voir le dossier, ainsi que ses sous-répertoires.

Par ailleurs, je vous conseille de faire un dossier dédié aux films, un autres aux séries, un autre aux dessins animés, un autre aux anime... Cela sera bien plus facile à gérer dans le futur.

How to install Plex Media Server in a Proxmox Linux Container (LXC)

Proxmox containers are a lightweight alternative to fully Virtualized Machines (VMs).We will in this guide show how Plex Media Server can be installed in aLinux Container (LXC).

GeekBitZoneGeekBitZone

Table of Contents

• Introducing Linux Containers (LXC)
• Privileged vs Unprivileged
• Software Versions Used
• Templates
• Debian
• Creating the Container
• Configuration
• Updating the System
• Installing Plex
• Logging into Plex
• Adding Media to Plex
• Option 1: Mounting an SMB/CIFS share
• Installing cifs-utils
• Creating CIFS Credentials
• Creating the Mount Directory
• Retrieving Plex uid and gid
• Systemd
• Option 2: Mounting an NFS Share
• Enabling NFS Container Support
• Installing nfs-common
• Creating the Mount Directory
• Adding fstab Entries
• Mounting the Volume
• Option 3: Mounting a Directory on the Proxmox host
• The pct Command
• Changing File Ownership
• Launching the Container
• Completing the Setup
• Summary
• References

How to install Plex Media Server in a Proxmox Linux Container (LXC)

Proxmox containers are a lightweight alternative to fully Virtualized Machines (VMs). We will in this guide show how Plex Media Server can be installed in a Linux Container (LXC).

Introducing Linux Containers (LXC)

Linux Containers (LXC) use the kernel of the host system instead of emulating a full Operating System (OS). This means that containers can access resources on the host system directly and at much lower memory cost. As an example, Plex Media Server running in a VM can easily fetch several Gigabytes of RAM, while in a container, the same installation uses only a few of hundred Megabytes.

Privileged vs Unprivileged

LXC Containers can be of two kinds; privileged and unprivileged. In a privileged container you will be able to modify resources that exist outside the container, while in an unprivileged container, it is only possible to modify external resources once the host has given its explicit permission.

We will in this tutorial cover privileged containers only due to their ease of use and by assuming that your Proxmox environment resides on a non-public facing, trusted Local Area Network (LAN). If you are concerned about security; use unprivileged containers, but be aware that you cannot delete any external files from inside the Plex Media Server container*.

Based on the information provided by this guide.

Software Versions Used

At the time of writing, the following software versions were used:

• Proxmox VE 7.3-3
• Debian 11 Bullseye (standard) 11.3-1

We have further assumed that Plex Media Server will be installed on a default Proxmox configuration with one node and one hard drive.

Templates

With the formalities out of the way, let’s go ahead and download our first LXC Template.

Pick a storage area for the container. We have chosen the local disk; local (pve) [1] and then selected CT Templates [2], followed by the Templates [3] button.

Debian

Plex Media Server can run on many platforms, but we prefer Debian, and more specifically the debian-11-standard 11.3-1 [1] template, because it is stable, secure and the base for many other Linux distributions, such as Ubuntu.

Once you have selected the template, press Download [2].

Close the Task Viewer once the download is complete.

Creating the Container

We are now ready to create the LXC Container. Press the Create CT button in the upper-right corner.

Set CT ID [1] to a number of your choice*. We have chosen 100 and given our Hostname [2] the name plex.

If you want the option to be able to delete external files from within Plex Media Server, set Unprivileged container [3] to off, i.e. make it a Privileged container.

Finally, enter and confirm your super-secret Password [4][5].

Press Next [6].

*Container numbers start from 100 to “infinite” and cannot overlap with existing containers or VMs.

Select debian-11-standard_11.3-1_amd64.tar.zst (the file that you just downloaded), from the Template [1] list.

Press Next [2].

Optional: Adjust Disk size if you intend store your media inside the LXC Container (not recommended), or if you need more space for metadata and thumbnails.

Press Next.

Optional: Set the number of CPU Cores. We are just using 1 core in this example, but adjust higher if you think you will need more power.

Press Next.

Optional: The Plex container can run with only 512 MiB RAM, but adjust here if you think more memory will be required.

Press Next.

We will access the Plex Media Server interface via IPv4 DHCP [1], but you can also leave it at static if you do not have the option (or do not want) to create a Static DHCP reservation on your router.

Press Next [2].

We will let our router handle DNS queries, but adjust here if necessary.

Press Next.

Confirm that all settings are okay and tick Start after created [1].

Press Finish [2].

Close the Task Viewer once confirmed that the container has been created.

Your LXC Container should now be ready and up and running.

Configuration

We are now ready to log in to the container.

Navigate to 100 (plex) [1] and select Console [2].

Login as root, followed by your super-secret Password.

root
<password>

Updating the System

There is a good chance the default software packages that came with the Debian 11 template are out-of-date. We will therefore update the APT repository to ensure we have the latest list of packages.

In the terminal window, type:

apt update

Followed by the upgrade command:

apt upgrade -y

Installing Plex

Plex Media Server is not included, by default, in Debian’s APT repositories, which means that it will have to be downloaded separately from Plex.tv’s servers.

We will first, however, need to install curl to enable fetching of URLs and gnupg for secure authentication:

apt install curl gnupg -y

To install Plex, a repository file must be created that pulls directly from the Plex repository. But first, a GPG key must be imported with the curl command and saved under /usr/share/keyrings/plex.gpg.

curl -sS https://downloads.plex.tv/plex-keys/PlexSign.key | gpg --dearmor | tee /usr/share/keyrings/plex.gpg > /dev/null 

Next, add the Plex repository to the standard APT sources directory.

echo "deb [signed-by=/usr/share/keyrings/plex.gpg] https://downloads.plex.tv/repo/deb public main" > /etc/apt/sources.list.d/plexmediaserver.list

Plex Media Server is now first class citizen in our APT repository, which means that we can go ahead and install the package as normal with the following command:

apt update && apt install plexmediaserver -y

Optional: Reboot the container to ensure that any currently locked process are re-initialised after the package update.

reboot

Log back in with your credentials.

root
<password>

Verify that Plex is active (running) with the systemctl command:

systemctl status plexmediaserver

The eagle-eyed user might see the following, rather worrisome, error message:

Critical: libusb_init failed

After some Google-Fu:ing we ended up on the following Reddit page which provided an explanation as to why the error is shown, but the suggested solution did not work in our case. libusb is, however, only used for Plex’s DVR functionality, and should not affect standard movie watching. If you do have a work-around, please post it in the comments below, and we will update this article.

(Press q on the keyboard to exit this screen.)

Logging into Plex

The Plex Media Server service is now up and running and we should be able to launch a web browser to access its web interface.

First we need to find out the IP address for our server:

ip a

Our container’s IP address resolves to 192.168.5.206, so we will use that, followed by Plex’s standard port number, 32400, and /web directory when typing the URL in our browser:

https://<your_plex_server_url>:32400/web

If you typed in the correct address, you will be automatically redirected to https://app.plex.tv for login authentication.

Go ahead and sign in with your Username and Password and then press the Sign In button.

Yep, we Got It!

Give your server a friendly Name [1], such as plex.

Optional: We will not allow Plex to automatically configure our network for outside access as there are much better (and safer) ways to access your home network, such as through a VPN.

Press Next [2].

Adding Media to Plex

We are now ready to add our legally downloaded media files to Plex.

Press Add Library.

Let’s start with some Films.

Press Next.

To add your movies, Press the Browse for Media Folder button.

Wait a minute! Where are my movie files?!

Unless you are storing your entire movie library inside the LXC Container (not recommended), you will need to find a way to access your files from outside the container. There are several ways that this can be done.

If your files reside on a Network Attached Storage (NAS), it is common to access them via the SMB/CIFS or NFS protocols.

If the files are in a directory on the Proxmox host, they can be directly mounted in the host onto the container.

We will in the next three sections explain the most common methods for how files can be accessed from inside the LXC Container. Please follow along with the option that applies to your specific network setup.

• Option 1: Mounting an SMB/CIFS share
• Option 2: Mounting an NFS Share
• Option 3: Mounting a directory on the Proxmox host

Option 1: Mounting an SMB/CIFS share

The SMB/CIFS protocol provides support for cross-platform file sharing with Microsoft Windows, OS X, and other Unix systems.

Installing cifs-utils

Let’s return to the container’s console and install the cifs-utils package.

apt install cifs-utils -y

Creating CIFS Credentials

Once cifs-utils have been downloaded, create an empty text file and place it under /root/.cifs_credentials. We prefer nano, but use whichever text editor you are comfortable with.

nano /root/.cifs_credentials

Inside the file, add your SMB/CIFS username=<username> on the first line and password=<password> on the second line.

Tip: (Ctrl+o saves the file and Ctrl+x exits the editor.)

username=<username>
password=<password>

Optional: Increase security by adjusting the read/write permissions on the file to the current owner only.

chmod 600 /root/.cifs_credentials 

Creating the Mount Directory

Create a directory in which we will mount our SMB/CIFS share. As we are using Plex, let’s give the directory the appropriate name;/mnt/plex.

mkdir <directory>

Retrieving Plex uid and gid

This step is necessary if you want to allow deletion of media files from within Plex Media Server.

When a directory is mounted it will belong to the user who first mounted it. In our example, the owner is root, while Plex Media Server runs as user plex. It will therefore not be able to modify any files belonging to root unless ownership is changed during the mount process.

In order to do so we need to first retrieve the User ID (uid) and Group ID (gid) of user plex. Execute the following command and write these numbers down because they will be used in the next section:

id -u plex && id -g plex

Systemd

We will mount our network share with systemd, rather than fstab, because the latter does not seem to remount on reboot as discussed in this Reddit post.

Under /etc/systemd/system/, create a new unit configuration file (.mount) that inherits its name from the full path to your mounted directory, with the quirk that all forward slashes / are replaced with a hyphen -.

Example 1: Your plex directory resides under /mnt/plex. Your unit configuration file should therefore be called /etc/systemd/system/mnt-plex.mount.

Example 2: A randomly shared folder under /home/geek/Public/important_files must be called /etc/systemd/system/home-geek-Public-important_files.mount and nothing else!

Armed with this information, let’s go ahead and create the file:

nano /etc/systemd/system/<directory-with-hyphen>.mount

Add the following information and replace <server_path>, <share>, <mount_point>, <uid> and <gid> as necessary.

Save and close the file.

[Unit]
  Description=Plex Media Server files
  Requires=network-online.target
  After=network-online.service

[Mount]
  What=//<server_path>/<share>
  Where=/<mount_point>
  Options=credentials=/root/.cifs_credentials,uid=<uid>,gid=<gid>
  Type=cifs

[Install]
  WantedBy=multi-user.target

Enable the unit configuration file:

systemctl enable <directory-with-hyphen>.mount

Start the directory service to automatically mount the folder:

systemctl start <directory-with-hyphen>.mount

Verify that the files are now seen in the mounted directory.

ls -l <mount-path>

Great, the files are there, and we can now go ahead and add this folder to Plex Media Server in Completing the Setup.

If you are using NFS shares instead, read on for Option 2: Mounting an NFS Share.

Caution: If you are continuing from Option 1: Mounting an SMB/CIFS share, please reset the container first and restart the tutorial from the Configuration section. Your mounted directory will otherwise be mapped twice with different protocols!

Option 2: Mounting an NFS Share

Network File System (NFS) is a distributed file system, which in comparison to SMB/CIFS, has better performance when medium-sized or small files are accessed.

If your LXC Container is still running, please turn it off with the Shutdown button.

Enabling NFS Container Support

Assuming that you are using a Privileged container, click on 100 (plex) [1], then Options [2] and double-click on Features [3].

Enable NFS [1] and press OK [2].

Features should now display mount=nfs.

Go back to 100 (plex) [1], Console [2] and Start [3] the container.

Log back in with your credentials.

root
<password>

Installing nfs-common

Once logged in, install the nfs-common package.

apt install nfs-common -y

Creating the Mount Directory

Create a directory in which we will mount our NFS share. As we are using Plex, let’s give the directory the appropriate name;/mnt/plex.

mkdir <directory>

Adding fstab Entries

NFS shares in LXC Containers can be mounted via /etc/fstab, so we will go ahead and edit this file:

nano /etc/fstab

Add the following information by replacing <server_path>, <share> and <directory> with your own network share settings and then save and close the file.

<server_path>:/<share>       /<directory>       nfs     defaults        0       0

Mounting the Volume

We can now mount the directory in /etc/fstab with the mount -a command.

mount -a

Verify that the files are now seen in the mounted directory.

ls -l <mount-path>

Yep, the files can be seen and the directory will remain mounted even after a reboot.

You can now jump to Completing the Setup or read on for Option 3: Mounting a Directory on the Proxmox host.

Caution: If you are continuing from Option 2: Mounting an NFS Share, please reset the container first and restart the tutorial from the Configuration section. Your mounted directory will otherwise be mapped twice with different protocols!

Option 3: Mounting a Directory on the Proxmox host

The final option that we will discuss is how to mount an LXC container directory directly from within the Proxmox host.

If your LXC Container is still running, please turn it off with the Shutdown button.

We will now open a terminal directly on the Proxmox host. (Note: not on the container).

Select pve [1] and open up a new Shell [2].

The pct Command

Let’s assume that our media files are stored in the following directory on the Proxmox host, /mnt/plex.

We can now tell Proxmox to mirror this local directory onto the LXC Container with this simple Proxmox Container Toolkit (pct) command:

Replace <id>, <source> and <target> with your own specific parameters.

pct set <id> -mp0 <source>,mp=<target>

Changing File Ownership

If you want the option to be able to delete external files from within Plex Media Server, change the ownership of the mount directory to plex.

Note: We are currently uncertain whether this is the correct way to change ownership for directories inside LXC Containers. If you aware of a “better” method, please let us know in the comments below and we will update this section. For now, it seems to work for what we are trying to do.

chown -R plex:plex /mnt/plex/

Launching the Container

Let’s exit our Proxmox shell and return to the web interface and select 100 (plex) [1], Resources [2] to verify that the Mount Point (mp0) [3] has been set to /mnt/plex,mp=/mnt/plex.

Good, it is there.

Go back to 100 (plex) [1], Console [2] and Start [3] the container.

Verify that the files are now seen in the mounted directory.

ls -l <mount-path>

Great, the files are there, and we can now continue to Completing the Setup.

Completing the Setup

Select your media folder and press Add.

Once you have finished adding the folders, press Add Library.

When you are done, press Next.

If you need to get some Plex Apps, do that here and then press Done.

Press Finish Setup.

Congratulations! Plex Media Server is now up and running in the LXC Container, and it has also full access to the files on your network.

26 commandes Docker les plus courantes avec exemples

Aide-mémoire de la commande Docker pour l’administrateur système et les développeurs ... Docker est un système de conteneurisation qui empaquete et exécute l’application avec son

GeekflareAvi

Trouver la version

L'une des premières choses que vous voulez savoir est de savoir comment trouver la version de docker installée

docker --version

Qu'est-ce qui tourne ?

ps répertorie tous les conteneurs Docker exécutés avec les détails du conteneur.

docker ps

ps-a

Répertoriez tous les conteneurs Docker en cours d'exécution / sortis / arrêtés avec les détails du conteneur.

docker ps -a

Supprimez le conteneur Docker avec l'ID de conteneur mentionné dans la commande.

docker rm 9b6343d3b5a0

Supprimez l'image docker avec l'ID d'image docker mentionné dans la commande

docker rmi fce289e99eb9

Redémarrez le conteneur Docker avec l'ID de conteneur mentionné dans la commande.

docker restart 09ca6feb6efc

Arrêtez un conteneur avec l'ID de conteneur mentionné dans la commande.

docker stop 09ca6feb6efc

Cette commande dans docker démarre le conteneur docker avec l'ID de conteneur mentionné dans la commande.

docker start 09ca6feb6efc

La commande Docker stop arrête le conteneur en douceur, c'est la différence entre les commandes kill et stop.

docker kill 09ca6feb6efc

Vaultwarden in Proxmox LXC Container

In a world of data breaches and password leaks, it is important to use a password manager and not using the same password for every account. Something that I have failed to do until this year. I know, I know how dare I. Like most people I used the builtin password manager in the web browser; then do…

Michael Schaecher

Before We Begin

Before we begin, I am assuming that you have a Proxmox server setup and running. If you do not have a Proxmox server setup and running then I recommend you checking Proxmox Setup Guide . It is dense but it is a good read and will help you understand Proxmox better.

Picking a Container Template

Proxmox has a lot of container templates to choose from. I am going to be using the Debian 12 (Bookworm) template.

You well want to click on Datacenter and then Storage and then click on local. Find the “CT Templates” and click on it this well bring up a list of all the container templates available to you locally. If you have not downloaded any templates then you well see nothing.

Locate the Templates button. Find and highlight the Debian 12 (Bookworm) template and click on the Download button. This well download the template to your local storage. You can download an template you want just as long you able to install Podman . I well be using Debian, so all applications are installed using apt.

Setting up the Container

Creating a Container

Now that we have a container template downloaded we can create a container. Click on the Create CT button. This well bring up a window that well allow us to create a container.

You well want to leave the Node and CT ID as the default, this well be helpful for finding the backup of the container. What you well want to set is the hostname and password and SSH key if you have one.

NOTE: You may need to enable root login in /etc/ssh/sshd_config by setting PermitRootLogin to yes and then restarting the ssh service after the container is booted. Otherwise you well not be able to login over ssh.

The root password doesn’t have to be complex, but it is recommended that it not be too simple. Lastly make sure that nesting is enabled and unprivileged is disabled.

Next we well want to set the Template to the template we downloaded earlier. The next thing is setting up the disk. I recommend setting the Disk size to 24GB, this well give you plenty of space for the container and the data that well be stored by the MariaDB database. Plus set mount option to noatime.

The CPU is next. You can leave the cores and sockets as the default value of 1 core if you wish.

Setting up the memory is next and this is different from setting up the memory for a VM. With LXC Containers you only need to set the memory and swap to what the container may need. The rest is shared with the host. I do recommend setting the memory to at least 1GB (1024MB) for both the memory and swap.

When it comes to networking you can leave network name and bridge as the default. However, you well want to set the IP address to a static IP address, outside of the DHCP range of your router is recommended. You well also want to set the Gateway to the IP address of your router.

The IP address and Gateway depends on your network setup the default gateway is 192.168.1.1 or 192.168.0.1. This means that the IP address of the container should be something like 192.168.1.100/24 or 192.168.0.100/24. The /24 is the subnet mask and is the default for most home networks.

The last two things to setup is the DNS which you can leave alone and confirming the settings. Once you have confirmed the settings click on the Create button. This well create the container and start it. You well want to however, leave the Start after created unchecked because we need to make some changes to the container before we start it.

Click the Finish buttom and wait for the container to be done baking. Once done there are some changes that we need to make to the container before we start it.

Fixing Options

Now that the container is created we need to make some changes to the container before we start it. Click on the container and then click on the Hardware tab. Find the Serial Port and click on the Add button. This well bring up a window that well allow us to add a serial port to the container.

The following options well need to be edited:

If you are wondering why the Nesting needs to enable here even though we enabled it when we created the container, that is because we disabled unprivileged.

Starting the Container

Now that we have made the changes to the container we can start it. Click on the >_Console button. This well bring up a console window that well allow us to login to the container. Now start the container.

Once the container is started you well be greeted with a login prompt. Login with the username root and the password that you set when you created the container.

Updating the Container

A LXC container is just a chroot environment and is not a full VM nor like a Docker/Kubernetes container. This means that you can keep the container up to date with the latest packages from the repositories.

apt update && apt dist-upgrade -y

Install the following packages:

apt install -y curl podman mariadb-server

Edit the /etc/ssh/sshd_config file and set PermitRootLogin to yes and then restart the ssh service.

PermitRootLogin yes

To paste into the console window you can use Ctrl + Shift + V or Right Click and then click on Paste. Once you have pasted the text into the console window you can save the file by pressing Ctrl + s to save the file and then Ctrl + x to exit the editor.

systemctl restart ssh

Set the date and time to your timezone. For me that is America/Boise.

timedatectl set-timezone America/Boise

Once everything is updated you can reboot the container by clicking on the drop down menu next to the Shutdown button and then click on Reboot and login over ssh.

Setting up MariaDB

Now that the container is up to date we can start setting up MariaDB. MariaDB is a fork of MySQL and is a relational database management system. It is used by Vaultwarden to store the data that you enter into the web interface and the clients, like the username and password’s plus identity and payment information.

mysql_secure_installation

This well start the MariaDB setup wizard. You well be asked to set the root password, remove anonymous users, disallow root login remotely, remove test database and access to it, and reload privilege tables. You can leave the root password blank if you wish, but I recommend setting a password. Use the same password that you set for the container.

Answer N to not use unix_socket authentication plugin.

Answer N if you don’t want to change the root password.

Answer Y to remove anonymous users.

Answer Y to disallow root login remotely.

Answer Y to remove test database and access to it.

Answer Y to reload privilege tables.

Creating the Database

Now that MariaDB is setup we can create the database for Vaultwarden with mariadb command.

CREATE DATABASE vaultwarden;

CREATE USER 'vaultwarden'@'localhost' IDENTIFIED BY 'password';

Replace password with a strong password that you can remember. You well need this password later when we setup Vaultwarden.

GRANT ALL PRIVILEGES ON vaultwarden.* TO 'vaultwarden'@'localhost';

Enter quit to exit the MariaDB shell.

Using Podman to run Vaultwarden

You well notice that you well be using a Docker container to run Vaultwarden. This is because Podman is a drop in replacement for Docker and is more secure because it does not require root privileges to run containers. Therefore it doesn’t have its own init system. It is that lack of an init system that make podman more compatible with LXC containers. This is because LXC containers use the host’s init system and that is why we need to enable nesting and disable unprivileged when we created the container earlier.

Creating the Vaultwarden Container

Now that we have MariaDB setup we can create the Vaultwarden container. We well be using Podman to create and run the container, but first we need to create a directory to store the data that Vaultwarden well use mkdir /vlt/. This well create a directory called vlt in the root directory of the container.

podman run \
  -d \
  --name vaultwarden \
  --network host \
  -v /vlt/:/data/:Z \
  -e ROCKET_PORT=80 \
  -e DATABASE_URL='mysql://vaultwarden:password@127.0.0.1:3306/vaultwarden' \
  -e ADMIN_TOKEN="$(echo -n 'admin_token' | argon2 "$(openssl rand -base64 32)" -e -id -k 65540 -t 3 -p 4)" \
  docker://vaultwarden/server:latest

Replace password with the password that you set for the MariaDB database.

The ADMIN_TOKEN is a secret string that is used to access the admin console. If the command fails then you may need to install argon2 with apt install -y argon2, then rerun the command. Don’t worry about the argon2 command it is just a password hashing utility for the ADMIN_TOKEN that you picked. Just remember to replace admin_token with a secret string that you can remember.

What do all the options mean?

If you were setting the up on a VM or a physical machine with other services running on it then you would want to use a different port and not use the host’s network, but a bridged network instead. However, since we are using a LXC container and nothing else is running on the container then we can use the host’s network with no issues. I also recommend using port 80 because it is the default port for http which easier to forward with a reverse proxy like Traefik or enginx .

Another options and it is one that I use is Cloudflare Tunnel . This allows me to use a domain name and have it point to my home network. This is great because I don’t have to worry about my ISP changing my IP address and having to update the DNS records. To learn more about Cloudflare tunnel check out official documentation .

I have mine running on a Raspberry Pi 3B, but a Zero W or Zero 2 W well work just as well.

I may do a post on how I setup Cloudflare Tunnel in the future.

Setup Your First Vaultwarden User Account

If you see a long string of numbers and letters then you have successfully created the container. If you see an error then you may have mistyped something. You can check the logs of the container by running podman logs vaultwarden.

Since this is the first time that you have run Vaultwarden you well need to create an account. Click on the Create Account button and enter your email address and password. You well need to confirm your email address before you can login.

NOTE: The email address does not have to be a real email address. However, if you wish to setup email notifications then you well need to use a real email address.

The master password should be a phrase that you can remember. If it is something that is common then use numbers, symbols, spaces, and capital letters. This well make it harder for someone to guess your master password.

After clicking on the Create Account button you well be taken to the login page. Enter your email address and password and click on the Login button.

Importing Passwords

Importing passwords is easy, figure out what how to export your passwords from a web browser is the hard part since every browser is different. Because of this I well not go over how to export passwords from a web browser or from another password manager. That is something that you well have to figure out on your own.

Just know that vaultwarden supports importing passwords from other password managers and web browsers in multiple formats. You can find the list of supported formats here .

Making Vaultwarden Persistent

Now that we have Vaultwarden setup and running we need to make it persistent so that it starts when the LXC container restarts or the host rebooted Vaultwarden well start automatically. To do this we need to create a systemd service file using podman.

 podman generate systemd --name vaultwarden > /usr/lib/systemd/system/vaultwarden.service

I like to use the /usr/lib/systemd/system/ directory for my systemd service files. You can use the /etc/systemd/system/ directory if you wish.

Now enable and start the service systemctl enable --now vaultwarden.service.

That is it you have successfully setup Vaultwarden in a LXC container on Proxmox. Now you can use the official clients to access your passwords and other sensitive information.

Pour activer votre licence, il vous suffit de vous rendre sur votre dashboard Portainer et de cliquer sur le bandeau orange « Upgrade to Business Edition ». Une pop-up s’ouvre, collez simplement votre licence et patientez quelques minutes pour la mise à jour.

sudo apt-get update && sudo apt-get upgrade

Étape 2 : Télécharger le script d’installation et installer Docker sur Raspberry Pi
Passez au téléchargement du script d’installation avec :

curl -fsSL https://get.docker.com -o get-docker.sh

Exécutez le script

sudo sh get-docker.sh

La sortie vous dira quelle version de docker est installée

Étape 3 : Ajouter un utilisateur non root au groupe Docker

Par défaut, seuls les utilisateurs qui ont des privilèges administratifs (utilisateurs root) peuvent exécuter des conteneurs. Si vous n’êtes pas connecté en tant que root, une option consiste à utiliser le préfixe sudo.

La syntaxe pour ajouter des utilisateurs au groupe Docker est la suivante :

sudo usermod -aG docker [user_name]

Pour ajouter l’utilisateur Pi, utilisez la commande

sudo usermod -aG docker pi

Installation de portainer sur raspberry

sudo docker run -d -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v /home/pi/volume1/portainer:/data portainer/portainer-ce:latest

sudo apt-get purge docker-ce docker-ce-cli containerd.io

Delete all images, containers, and volumes:

sudo rm -rf /var/lib/docker
sudo rm -rf /var/lib/containerd

Remove previous versions:

sudo apt-get remove docker docker-engine docker.io containerd runc

Remove docker completly

dpkg -l | grep -i docker
sudo apt remove --purge docker-ce docker-ce-cli containerd.io
sudo rm -rf /var/lib/docker
sudo rm -rf /var/lib/containerd
sudo apt autoremove -y
sudo apt autoclean

                                                                             presence_detection                                                                                  

!/bin/sh

mac=$1
idx=$2
device_present=Off
domoticz_status=curl -s "http://xxxx:xxxx@xxxx.xxx.0.xxx:xxxx/json.htm?type=devices&rid=$idx" | grep Status | awk '{print $3}' | sed 's/[",]//g'
for x in wl -i eth1 assoclist | awk '{print $2}'; do
if [ $x = $mac ]; then
device_present=On
fi
done

look in 5GHz (eth2) network for device

for x in wl -i eth2 assoclist | awk '{print $2}'; do
if [ $x = $mac ]; then
device_present=On
fi
done
echo "Domoticz: $domoticz_status, router: $device_present"

tell domoticz the new device status

if [ $domoticz_status != $device_present ]; then

if [ $device_present = "On" ]; then curl -s "http://xxxx:xxx@xxx.xxx.0.xxx:xxxx/json.htm?type=command&param=switchlight&idx=$idx&switchcmd=On" > /dev/null

else curl -s "http://xxx:xxx@xxx.xxx.0.xxx:xxxx/json.htm?type=command&param=switchlight&idx=$idx&switchcmd=Off" > /dev/null

fi

fi

Yet another presence detection method - Domoticz

DomoticzPost

L'étoile active la page par défaut du site web