similar to: C7 and docker storage

Gianluca Cecchi <gianluca.cecchi at gmail.com> wrote: > Date: Thu, 30 Nov 2017 09:55:58 +0100 > On Wed, Nov 29, 2017 at 10:23 PM, <m.roth at 5-cent.us> wrote: > >> The latter would explain the message my user's job gave him when it tried >> to umount / >> >> A bit of googling, and I see something called overlayFS can be used... but >> I know

Hello, i want to use docker with ipv6. i install docker and edit the /etc/docker/daemon.json: { "ipv6": true } Message: [root at froodo network-scripts]# systemctl status docker ? docker.service - Docker Application Container Engine Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Do

On Wed, Sep 02, 2020 at 11:56:58PM +0000, Chen Wenwei wrote: > Found pkg-config: /usr/local/bin/pkg-config (0.29.2) > Did not find CMake 'cmake' > Found CMake: NO > Run-time dependency libapparmor found: NO (tried pkgconfig and cmake) > Library attr found: YES > Library audit found: YES > Run-time dependency bash-completion found: YES 2.1 > Run-time dependency blkid

# HG changeset patch # User Ryan Grimm <grimm@us.ibm.com> # Date 1156190589 18000 # Node ID a19a066dea764a70f06b4e4341229db92c2eb5c3 # Parent 53c5bcecfcfdb70cb3a2aed0adb564312988fbdd dm-userspace internal libdmu support for userspace tool Signed-off-by: Ryan Grimm <grimm@us.ibm.com> Signed-off-by: Dan Smith <danms@us.ibm.com> diff -r 53c5bcecfcfd -r a19a066dea76 tools/Makefile

The CentOS Atomic SIG has released an updated version (https://wiki.centos.org/SpecialInterestGroup/Atomic/Download) of CentOS Atomic Host (7.1708), a lean operating system designed to run Docker containers, built from standard CentOS 7 RPMs, and tracking the component versions included in Red Hat Enterprise Linux Atomic Host. This release, which is based on the RHEL 7.4 source code

This commit deprecates luks-open/luks-open-ro/luks-close for the more generic sounding names cryptsetup-open/cryptsetup-close, which also correspond directly to the cryptsetup commands. The optional cryptsetup-open readonly flag is used to replace the functionality of luks-open-ro. The optional cryptsetup-open crypttype parameter can be used to select the type (corresponding to cryptsetup open

This commit deprecates luks-open/luks-open-ro/luks-close for the more generic sounding names cryptsetup-open/cryptsetup-close, which also correspond directly to the cryptsetup commands. The optional cryptsetup-open readonly flag is used to replace the functionality of luks-open-ro. The optional cryptsetup-open crypttype parameter can be used to select the type (corresponding to cryptsetup open

The main goal of these patch series is to implement a new API that allows to retrieve created device-mapper devices for volumes and partitions back after they have been created. As part of this patch: - required libdevmapper version was bumped to 1.02. I think it is safe because it was released more then 10 years ago; - newer version of libdevmapper allowed to simplify code base a little bit; -

Dear all, I'm moving my first baby steps with libvirt-lxc trying to convert over from an LXD installation and one of the hurdles is putting together an image. All the examples I found about libvirt-lxc refer to running /bin/sh in a container, almost as if it was docker, as opposed to run a "full system" like I've been doing with lxd. Also virt-install, often referred in libvirt

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

GCC has two warnings related to large stack frames. We were already using the -Wframe-larger-than warning, but this reduces the threshold from 10000 to 5000 bytes. However that warning only covers the static part of frames (not alloca). So this change also enables -Wstack-usage=10000 which covers both the static and dynamic usage (alloca and variable length arrays). Multiple changes are made

On Monday 07 March 2016 11:18:32 Richard W.M. Jones wrote: > GCC has two warnings related to large stack frames. We were already > using the -Wframe-larger-than warning, but this reduces the threshold > from 10000 to 5000 bytes. > > However that warning only covers the static part of frames (not > alloca). So this change also enables -Wstack-usage=10000 which covers > both

Oliver Welter: > >after upgrading my mail server (dovecot 1.1.7 -> 2.2.13) I get tons of > >messages about corrupted index files in the syslog ("Error: Corrupted > >transaction log" and "Warning: fscking index file .. dovecot.index". > > > Some more debugging - I did a "fuser" on a broken dovecot.index file > and see a lot of stale

Some people contribute to someone specific fs testing mostly, record some of them as Reviewer. Signed-off-by: Zorro Lang <zlang at kernel.org> --- If someone doesn't want to be in cc list of related fstests patch, please reply this email, I'll remove that reviewer line. Or if someone else (who contribute to fstests very much) would like to a specific reviewer, nominate yourself to

Original version linked from here: https://bugzilla.redhat.com/show_bug.cgi?id=1808977#c8 There is no change in the code in this series, but feedback from the original series was we shouldn't lose the error message in patch 7. When I tested this just now in fact we don't lose the error if debugging is enabled, but I have updated the commit message to note what the error message is in the

These commits, along with the associated changes to common: https://www.redhat.com/archives/libguestfs/2020-March/msg00286.html support the transparent decryption and inspection of Windows guests encrypted with BitLocker encryption. To do the BitLocker decryption requires cryptsetup 2.3.0 (although cryptsetup 2.3 is not required for existing LUKS use). It also requires a new-ish Linux kernel, I

Hello Experts, I'm trying to compiling libvirt 6.0.0 on an CentOS 8 env by following the guide here. (https://libvirt.org/compiling.html#compiling) When running the configure command, i encountered the issue of showing "configure: error: Unable to find <rpc/rpc.h>": How can i let the configure command to realize the non-standard header file location of portablexdr

Last week, the CentOS Atomic SIG released an updated version (https://wiki.centos.org/SpecialInterestGroup/Atomic/Download) of CentOS Atomic Host (7.1707), a lean operating system designed to run Docker containers, built from standard CentOS 7 RPMs, and tracking the component versions included in Red Hat Enterprise Linux Atomic Host. The release, which came as part of the monthly CentOS release

As discussed in the emails today, this is the third version addressing most points from the v1/v2 review. You will need to pair this with the changes in libguestfs-common from this series: https://www.redhat.com/archives/libguestfs/2020-September/msg00050.html Rich.

I may have missed some overnight replies to my question from yesterday - if so, sorry. >From my googling, it looks like I should change from the loopback device to overlayFS (with overlay2). What I haven't found is, first and foremost, more clarity on configuring storage. It *appears* that the loopback storage is just a directory under /var/lib/docker (yet I see a reference in