create a lxc Debian bookworm guest into Debian host Trixie ``` lxc-create --name bookworm --template download -- --dist debian --release bookworm --arch amd64 lxc-start bookworm lxc-attach bookworm dpkg --add-architecture i386 apt-get update ```

https://linuxcontainers.org/lxc/

you find your bookworm under /var/lib/lxc/bookworm/rootfs/root/ 26.08.25 Basic Usage of lxc The simplest way to attach to the container is: ```bash lxc-attach bookworm ``` This will attach you to the container's console as the root user. You'll get a shell prompt inside the container. **Important Considerations and Troubleshooting:** 1. **Container Status:** Make sure the container is actually running. You can check with: ```bash lxc-info bookworm ``` Look for the "State" field. It should say "RUNNING." If it's not running, start it with: ```bash lxc-start bookworm ``` 2. **Permissions:** You might need `sudo` to run `lxc-attach`, especially if you're not part of the `lxc` group. Try: ```bash sudo lxc-attach bookworm ``` 3. **User:** By default, you attach as root. If you want to attach as a different user, use the `-n` flag: ```bash lxc-attach -n bookworm -- /bin/su - <username> ``` Replace `<username>` with the actual username inside the container. You might need to provide the user's password. Alternatively, you can use `sudo -u <username> -i` instead of `/bin/su`. 4. **Terminal Issues:** Sometimes, the terminal settings inside the container might not be compatible with your host terminal. This can result in a garbled display or other issues. Try these: * **Force a TTY:** Use the `-t` flag to force the allocation of a pseudo-terminal: ```bash lxc-attach -t bookworm ``` * **Set the Terminal Type:** Inside the container, try setting the `TERM` environment variable: ```bash export TERM=xterm ``` You can add this to the user's `.bashrc` or `.zshrc` file inside the container to make it permanent. Common values for `TERM` are `xterm`, `vt100`, or `linux`. 5. **Networking:** If you're having trouble connecting to the container's network from the host, make sure the container has a valid IP address and that networking is properly configured. Check the container's configuration file (usually located in `/var/lib/lxc/bookworm/config`) for network settings. 6. **LXC Version:** Make sure you have a reasonably recent version of LXC installed. Older versions might have bugs or compatibility issues. Check your version with: ```bash lxc-version ``` 7. **Container Configuration:** Sometimes, the container's configuration can cause issues. Double-check the configuration file (`/var/lib/lxc/bookworm/config`) for any unusual settings that might be interfering with `lxc-attach`. Pay particular attention to network and console settings. 8. **Alternative: `lxc exec`:** If `lxc-attach` is consistently giving you problems, consider using `lxc exec` as an alternative. It allows you to execute commands inside the container without directly attaching to its console. For example: ```bash lxc exec bookworm -- bash ``` This will start a new `bash` shell inside the container. The `--` is important to separate the `lxc exec` options from the command you want to run inside the container. **Example Scenario and Solution:** Let's say you're getting a blank screen after running `lxc-attach bookworm`. This is often a terminal issue. Here's what you could try: 1. `sudo lxc-attach -t bookworm` (Force a TTY) 2. If that doesn't work, attach using `lxc exec bookworm -- bash` 3. Once inside the container (using either method), run `export TERM=xterm` 4. Try `lxc-attach bookworm` again. By systematically checking these points, you should be able to diagnose and resolve most issues with `lxc-attach`. 26.08.25

https://linuxcontainers.org/lxc/manpages/man1/lxc-attach.1.html

• Home
• Notebook
• Contact us

• Privacy Statement
• 

Copyleft ☠ 2026