dm-crypt.saout.de archive mirror
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: dm-crypt <dm-crypt@saout.de>
Subject: [dm-crypt] Re: veritysetup and CentOS 8
Date: Fri, 15 Oct 2021 10:32:33 +0200	[thread overview]
Message-ID: <6d9171f8-9fd6-5f18-6df2-038e02a06c8a@gmail.com> (raw)
In-Reply-To: <PH0PR14MB4535F31A477EA666028C6B9AEDB89@PH0PR14MB4535.namprd14.prod.outlook.com>

On 14/10/2021 10:23, Wei, Catherine wrote:
> Hi all,
> 
> I found that the veritysetup built from cryptsetup-1.7.5 couldn’t work in CentOS 8.2, when I run veritysetup command on the CentOS 8, it reported error:
> 
>  
> 
> veritysetup: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by veritysetup)

This cannot happen, if you compile it properly.

Just use provided version from CentOS repo.

Also CentOS kernel has own options, not everything is available there (e.g. FEC support for dm-verity is not compiled in IIRC).

Anyway, this is upstream list, version 1.7.5 is 4 years old, why are you using that?
(CentOS8 stream repo provides 2.3.3, at least).

Milan
_______________________________________________
dm-crypt mailing list -- dm-crypt@saout.de
To unsubscribe send an email to dm-crypt-leave@saout.de

  reply	other threads:[~2021-10-15  8:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-14  8:23 [dm-crypt] veritysetup and CentOS 8 Wei, Catherine
2021-10-15  8:32 ` Milan Broz [this message]
     [not found] ` <68390b56-e5b7-7f3c-74a7-6edad253df08@gmail.com>
     [not found]   ` <PH0PR14MB4535EFBF30DF57ECB89E5E06EDBC9@PH0PR14MB4535.namprd14.prod.outlook.com>
2021-10-26  8:07     ` [dm-crypt] " Wei, Catherine
2021-10-26  8:13       ` Wei, Catherine
2021-10-30 10:19         ` Milan Broz
2021-11-10  6:28           ` Wei, Catherine
2021-11-10  9:42             ` Milan Broz

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=6d9171f8-9fd6-5f18-6df2-038e02a06c8a@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=dm-crypt@saout.de \
    /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 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).