Re:I'm “still afraid to use spaces in file names” years old
by fouric on Thursday November 11, 2021 @04:39PM
(#29193527)
Does Docker abstract filesystem behaviors like this? I always thought that it stopped at the libc level - that is, libc is included in the container, but it calls the host kernel's system calls, and so inherits the host kernel's behavior (including things like underlying filesystem case sensitivity).
[ Parent
| on HN ]
Re:I'm “still afraid to use spaces in file names” years old
by handrous on Thursday November 11, 2021 @05:09PM
(#29193851)
Docker relies on LXC, so it's Linux-only. On other platforms it runs in a Linux VM. The host for Docker, then, is Linux no matter where you are.
Re:I'm “still afraid to use spaces in file names” years old
by zokier on Thursday November 11, 2021 @07:14PM
(#29194907)
> Docker relies on LXC, so it's Linux-only.
Docker hasn't supported LXC since 2016, and stopped relying on it in 2014
https://www.docker.com/blog/docker-0-9-introducing-execution...
Re:I'm “still afraid to use spaces in file names” years old
by handrous on Friday November 12, 2021 @11:38AM
(#29201210)
I thought the name for the collection of kernel features was LXC, I didn't realize (until just now) that was the name only for the also-kernel-level wrapper for those features, which name does not cover the features themselves. That is, I didn't realize that LXC is to Cgroups+Namespaces as Libvirt is to KVM—I thought LXC, as a label, covered the whole feature-set—but regardless, it's still married to Linux kernel features and runs on other platforms under virtualization, no?
Re:I'm “still afraid to use spaces in file names” years old
by zokier on Friday November 12, 2021 @08:42PM
(#29206548)
> it's still married to Linux kernel features and runs on other platforms under virtualization, no?
Actually no. At least on Windows Docker can do native Windows containers too
https://poweruser.blog/lightweight-windows-containers-using-...