You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While reproducing the cve-2019-16884 I find it can't work. After digging into this it seems the runc version is wrong.
When I reproduce this issue in here opencontainers/runc#2128
I got following error:
cannot be mounted because it is located inside \\\"/proc\\\\
The runc version for this issue is docker-ce 18.03.1(runc 1.0.0-rc5).
If we use runc 1.0.0-rc6 it can work.
The reason that runc 1.0.0-rc6 can work because this change(linux: drop check for /proc as invalid dest): opencontainers/runc@636b664
So this issue can only trigger after 1.0.0-rc6.
Don't know the relation of docker-ce version and runc version.
Maybe we need to download runc and replace the docker-ce shipped runc.
Thanks,
Li Qiang
The text was updated successfully, but these errors were encountered:
While reproducing the cve-2019-16884 I find it can't work. After digging into this it seems the runc version is wrong.
When I reproduce this issue in here opencontainers/runc#2128
I got following error:
cannot be mounted because it is located inside \\\"/proc\\\\
The runc version for this issue is docker-ce 18.03.1(runc 1.0.0-rc5).
If we use runc 1.0.0-rc6 it can work.
The reason that runc 1.0.0-rc6 can work because this change(linux: drop check for /proc as invalid dest):
opencontainers/runc@636b664
So this issue can only trigger after 1.0.0-rc6.
Don't know the relation of docker-ce version and runc version.
Maybe we need to download runc and replace the docker-ce shipped runc.
Thanks,
Li Qiang
The text was updated successfully, but these errors were encountered: