| 1 |
On Tue, Feb 18, 2020 at 2:06 PM Nikos Chantziaras <realnc@×××××.com> wrote: |
| 2 |
> |
| 3 |
> It gets worse. The container reconfigured the keyboard shortcuts on the |
| 4 |
> host! After booting a container, alt+Fn or alt+left/right on the host |
| 5 |
> started switching to the linux text-mode console. I pressed alt+f2 to |
| 6 |
> bring up the plasma search, I ended up on TTY2... ha ha. |
| 7 |
> |
| 8 |
> Remember how I said I'll use nspawn from now on? I take that back. Let's |
| 9 |
> just say this thing is not even remotely production ready. |
| 10 |
|
| 11 |
Never had any issues with it, but I've never tried to use my host root |
| 12 |
as the input filesystem. I suspect the issue is that this is giving |
| 13 |
the container access to the host /dev, /sys and so on, and thus the |
| 14 |
container isn't ending up being contained. Normally you don't go |
| 15 |
mounting a host /dev inside a container image before launching it... |
| 16 |
|
| 17 |
-- |
| 18 |
Rich |
Archives