All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.ibm.com>
To: Petr Vorel <petr.vorel@gmail.com>
Cc: linux-integrity@vger.kernel.org, Vitaly Chikunov <vt@altlinux.org>
Subject: Re: [PATCH ima-evm-utils 1/2] switch to using crun for podman
Date: Mon, 01 Nov 2021 14:39:26 -0400	[thread overview]
Message-ID: <4d0f219c941bf096658d78a95ca566a76b15b082.camel@linux.ibm.com> (raw)
In-Reply-To: <YXfwoOEZZKKII6s9@pevik>

Hi Petr,

On Tue, 2021-10-26 at 14:12 +0200, Petr Vorel wrote:
> Hi Mimi,
> 
> > Fix for:
> 
> > "container_linux.go:367: starting container process caused: error
> > adding seccomp filter rule for syscall bdflush: permission denied":
> > OCI permission denied"
> 
> I was surprised crun is updated but runc not, but LGTM.
> It'd be nice if somebody test it with public travis (I no longer have access).

Stefan tested on the public travis, which resulted in updating Alpine,
Fedora, and Alt to use podman and crun.  Other than the alt:sisyphus
image prompt, the tests all pass.  I assume this is intermittent.
    
     Please select an image:
      ▸ docker.io/library/alt:sisyphus
        quay.io/alt:sisyphus

> 
> Reviewed-by: Petr Vorel <petr.vorel@gmail.com>

thanks!

Mimi

> 
> IMHO from a long term perspective it'd be nice to create GitHub Actions profile
> (but that's not related to this patchset).




      reply	other threads:[~2021-11-01 18:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26  2:49 [PATCH ima-evm-utils 1/2] switch to using crun for podman Mimi Zohar
2021-10-26  2:49 ` [PATCH ima-evm-utils 2/2] upgrade to glibc-2.34 uses clone3 causing CI to fail Mimi Zohar
2021-10-26 14:30   ` Vitaly Chikunov
2021-10-26 22:07     ` Petr Vorel
2021-11-01  6:13     ` Dmitry V. Levin
2021-10-26 12:12 ` [PATCH ima-evm-utils 1/2] switch to using crun for podman Petr Vorel
2021-11-01 18:39   ` Mimi Zohar [this message]

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=4d0f219c941bf096658d78a95ca566a76b15b082.camel@linux.ibm.com \
    --to=zohar@linux.ibm.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=petr.vorel@gmail.com \
    --cc=vt@altlinux.org \
    /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. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.