mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: Yuri Kanivetsky <yuri.kanivetsky@gmail.com>
Cc: musl@lists.openwall.com
Subject: Re: [musl] faccessat() always return EPERM
Date: Sat, 24 Jul 2021 01:56:25 -0400	[thread overview]
Message-ID: <20210724055625.GN13220@brightrain.aerifal.cx> (raw)
In-Reply-To: <20210724014021.GM13220@brightrain.aerifal.cx>

On Fri, Jul 23, 2021 at 09:40:22PM -0400, Rich Felker wrote:
> On Sat, Jul 24, 2021 at 04:16:25AM +0300, Yuri Kanivetsky wrote:
> > Hi,
> > 
> > I'm not sure that it has something to do with musl. But experienced in
> > a Alpine Linux docker container (ruby:2.6-alpine3.14) on Debian 9 or
> > 10. I can't reproduce it with Alpine Linux 3.13 (container) or Debian
> > 8 (host).
> > 
> > For example, the following program outputs -1:
> > 
> > #include <stdio.h>
> > #include <fcntl.h>
> > #include <unistd.h>
> > 
> > int main()
> > {
> >     int r;
> >     r = faccessat(AT_FDCWD, "/", R_OK, AT_EACCESS);
> >     printf("%i", r);
> >     return 0;
> > }
> > 
> > I believe whatever is passed as the second parameter, it would return -1.
> > 
> > As a result at least irb and bundler doesn't work. Is this some sort
> > of binary incompatibility with Linux kernel?
> 
> 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.

I forgot to mention: if you can disable seccomp in Docker, that's a
workaround that doesn't require upgrading.

  reply	other threads:[~2021-07-24  5:56 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 [this message]
2021-07-24 23:36   ` Alex Xu (Hello71)
2021-07-27  4:34     ` Yuri Kanivetsky
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=20210724055625.GN13220@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    --cc=yuri.kanivetsky@gmail.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).