doc: dependencies: linux 3.18 #2282
Conversation
|
Could we add this to the list of known issues? currently at bottom of readme.md |
alban
force-pushed
the
alban/doc-dep-linux
branch
from
9604ba5 to
7cd7e81
Compare
|
Updated. |
| @@ -73,3 +73,5 @@ Some portions of the codebase are derived from other projects under different li | |||
| ## Known issues | |||
|
|
|||
| Due to a bug in the Linux kernel, using rkt's overlay support on top of an overlay filesystem requires Linux 4.3+. | |||
There was a problem hiding this comment.
Can we link to actual issues?
There was a problem hiding this comment.
(e.g. as an end user I'd find "In some configurations" a little frustratingly vague)
alban
force-pushed
the
alban/doc-dep-linux
branch
3 times, most recently
from
0bb03e0 to
8ae5421
Compare
|
@jonboulle Updated. Is it a better wording? |
|
s/bump/bumps/ |
|
Wording LGTM |
|
Sure seems fine. @joshix might have a tweak suggestion |
|
BTW, should we mention /var/lib/rkt on btrfs bug in the known issues section too? |
|
Yes!!!! On Wed, Mar 16, 2016 at 4:23 PM Krzesimir Nowak notifications@github.com
|
alban
force-pushed
the
alban/doc-dep-linux
branch
2 times, most recently
from
958e313 to
4005e5a
Compare
|
Updated. |
Linux 3.18 introduced the fix for unlinking files and directories that are mount points in another mount namespace. Before Linux 3.18, unlinking could return EBUSY: torvalds/linux@8ed936b With the introduction of rkt-fly, this becomes a visible issue with rkt gc, see discussion on: rkt#1922 (comment) This patch bumps the run-time dependency to Linux 3.18. This also documents the issues in README.md.
|
Looks great. Thanks. |
doc: dependencies: linux 3.18
|
So unless Red Hat backports some patches RHEL and derivatives are a no-go since they use 3.10? Debian Jessie is on 3.16 although 4.3 appears to be available from the backports, but I'm much less familiar with the Debian ecosystem. Ubuntu 14.04 is on 3.13. That seems like a pretty severe limitation. |
|
CentOS 7 is in the same boat. It's a very severe limitation. If this doc indicates that #1922 will not be fixed, we're not going to be able to adopt rkt in Mantl. So, is that the case? |
|
Note this is not to say that rkt won't work, just that certain functionality might be unavailable or have caveats (e.g. #1922 (comment)). We do want rkt to be as functional as possible on older OSes and we're actively discussing how to improve this, stay tuned. |
Linux 3.18 introduced the fix for unlinking files and directories that
are mount points in another mount namespace. Before Linux 3.18,
unlinking could return EBUSY:
torvalds/linux@8ed936b
With the introduction of rkt-fly, this becomes a visible issue with rkt
gc, see discussion on:
#1922 (comment)
This patch bumps the run-time dependency to Linux 3.18
/cc @jellonek @BrianHicks @jcollie