LXD, alternative Linux à Windows Sandbox
Mis à jour le
Notre avis
LXD is not a direct replacement for Windows Sandbox for average users due to higher complexity and setup requirements. While it can isolate untrusted programs in lightweight containers, it's designed for system administrators and developers managing containerized services, not one-click sandboxing. If you need fast, disposable environments with minimal configuration, LXD is overkill. However, advanced users who understand container networking and privilege settings can configure it securely for sandboxing. For most people wanting Windows Sandbox-like behavior, tools like Firejail or Bubblewrap are simpler and more appropriate.
- Licence
- GPL-2.0
- Prix
- Gratuit
- Dernière version
- 6.10.1
- Note
- —
Ce qui fonctionne pareil
- Provides isolation of untrusted programs from the host system
- Supports temporary environments that can be discarded after use
- Allows restricted access to host resources through configuration
- Offers network isolation capabilities when configured properly
- Enables fast startup and shutdown of container instances
Ce qui change
- LXD requires daemon setup and initial configuration, unlike Windows Sandbox's zero-setup approach
- No built-in one-click launch for untrusted executables
- Persistent storage must be explicitly disabled to match Windows Sandbox's ephemeral nature
- Primarily command-line driven with no native GUI
- More focused on server-style container management than desktop sandboxing
Ouvrir vos fichiers Windows Sandbox
Windows Sandbox does not produce exportable files or snapshots that can be opened in LXD. LXD uses its own image and container format, typically managed through its REST API or command-line tools. There is no compatibility between Windows Sandbox session data and LXD containers. If you need to analyze files from a sandboxed Windows environment, you must extract them manually before closing the session. LXD does not support importing or running Windows binaries directly.
Passer de Windows Sandbox à LXD, étape par étape
- Install LXD using your distribution's package manager (e.g., 'sudo apt install lxd' on Debian/Ubuntu)
- Initialize LXD with 'lxd init' and configure storage and network settings
- Create an ephemeral container image based on a minimal Linux distribution
- Launch the container with restricted network and filesystem access
- Run untrusted programs inside the container via 'lxc exec'
- Destroy or restart the container after use to reset state
Fonctionnalités clés de LXD
- Gestion de conteneurs basée sur un démon
- Création de conteneurs à partir d'images
- Prise en charge de la migration à chaud
- Prise en charge des backends de stockage ZFS et btrfs
- Gestion des volumes réseau et de stockage
- API REST pour l'automatisation
- Fonctionnalités d'instantané et de sauvegarde
- Prise en charge des conteneurs privilégiés et non privilégiés
Installer LXD sous Linux
sudo apt install lxdsudo pacman -S lxdQuestions fréquentes
Can I run Windows programs in LXD like in Windows Sandbox?
No. LXD runs Linux containers only. It cannot execute Windows binaries. You'd need Wine or a full virtual machine for Windows applications.
Is LXD as fast and temporary as Windows Sandbox?
Containers start quickly, but only if pre-configured. True ephemeral behavior requires setting 'ephemeral=true' at launch. Otherwise, changes persist until manually cleaned.
Do I need root privileges to use LXD?
Yes, LXD manages system containers and requires root access. Regular users must be added to the 'lxd' group to interact with it, which grants significant privileges.