From: Yuri Kanivetsky <yuri.kanivetsky@gmail.com>
To: "Alex Xu (Hello71)" <alex_y_xu@yahoo.ca>
Cc: musl@lists.openwall.com
Subject: Re: [musl] faccessat() always return EPERM
Date: Tue, 27 Jul 2021 07:34:38 +0300 [thread overview]
Message-ID: <CAMhVC3Zo8T2ODnG7B6QKfdneF9DDwb=89X5h2QRT7i1SBm6+4Q@mail.gmail.com> (raw)
In-Reply-To: <1627169764.w6a53kypz8.none@localhost>
Hi
On Sat, Jul 24, 2021 at 4:40 AM Rich Felker <dalias@libc.org> wrote:
>
> No, it's almost surely Docker blocking the operation with the wrong
> error code (EPERM):
>
> https://github.com/opencontainers/runc/issues/2151
>
> I'm not sure what the status on getting fix deployed is. It might go
> away if the host running Docker can upgrade.
Indeed. It seems to depend on docker version:
Debian 8 18.06.3-ce 0
Debian 8 18.06.3-ce 0
Debian 8 18.06.3-ce 0
Debian 8 18.06.3-ce 0
Debian 9 19.03.6 -1
Debian 9 19.03.13 -1
Debian 9 19.03.13 -1
Debian 9 19.03.14 -1
Debian 10 19.03.13 -1
Debian 10 19.03.13 -1
Debian 10 20.10.5 0
On Sat, Jul 24, 2021 at 4:57 AM Wolf <wolf@wolfsden.cz> wrote:
>
> Cannot reproduce over here, your sample program works for me in
> alpine 3.14 container running under podman.
What OS and docker version are you using?
On Sat, Jul 24, 2021 at 8:56 AM Rich Felker <dalias@libc.org> wrote:
>
> I forgot to mention: if you can disable seccomp in Docker, that's a
> workaround that doesn't require upgrading.
Indeed, `--security-opt seccomp=unconfined` or `security_opt:
[seccomp=unconfined]` (docker-compose) kind of resolve it.
On Sun, Jul 25, 2021 at 2:36 AM Alex Xu (Hello71) <alex_y_xu@yahoo.ca> wrote:
>
> https://wiki.alpinelinux.org/wiki/Release_Notes_for_Alpine_3.14.0#faccessat2
Good point.
next prev parent reply other threads:[~2021-07-27 4:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-24 1:16 Yuri Kanivetsky
2021-07-24 1:40 ` Rich Felker
2021-07-24 5:56 ` Rich Felker
2021-07-24 23:36 ` Alex Xu (Hello71)
2021-07-27 4:34 ` Yuri Kanivetsky [this message]
2021-07-24 1:56 ` Wolf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMhVC3Zo8T2ODnG7B6QKfdneF9DDwb=89X5h2QRT7i1SBm6+4Q@mail.gmail.com' \
--to=yuri.kanivetsky@gmail.com \
--cc=alex_y_xu@yahoo.ca \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).