Re: [CentOS] ZFS fails with latest C8 kernel
On Mon, Aug 10, 2020 at 01:43:00AM -0500, Robert G (Doc) Savage via CentOS wrote: > As if last weekend's UEFI debacle wasn't bad enough, it now seems the > latest C8 kernel (4.18.0-193.14.2) is incompatible with the current > ZFSOnLinux packages (0.8.4-1). When booted to the latest kernel, ZFS is > inaccessible on my C8 storage server. When I back off to the prior > kernel (4.18.0-193.6.3), all is well. please open an issue on zfsonlinux github: https://github.com/openzfs/zfs/issues and provide them a reproducible testcase. > > If a local ZFS system is unavailable to the C8 kernel support folks, > I'll be happy to assist them by volunteering my system as a lab rat. Imho, that's out of CentOS scope, unless some people are willing to work on it with zfsonlinux people. Cheers Tru -- Tru Huynh http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B pgp8sY4n_WBW8.pgp Description: PGP signature ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] ZFS fails with latest C8 kernel
On 8/10/20 1:43 AM, Robert G (Doc) Savage via CentOS wrote: > As if last weekend's UEFI debacle wasn't bad enough, it now seems the > latest C8 kernel (4.18.0-193.14.2) is incompatible with the current > ZFSOnLinux packages (0.8.4-1). When booted to the latest kernel, ZFS is > inaccessible on my C8 storage server. When I back off to the prior > kernel (4.18.0-193.6.3), all is well. > > If a local ZFS system is unavailable to the C8 kernel support folks, > I'll be happy to assist them by volunteering my system as a lab rat. CentOS does not support, and will not support ZFS (unless it is rolled into RHEL). Whatever packages you got for it .. they were written by ZFSOnLinux, not us. Ask them for an update. signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Docker container isolation not working in CentOS 7
Hi, I've decided to use these summer holidays to wrap my head around Docker and its quirks. Spent the last couple weeks working through a Udemy tutorial and a thick book about Docker, and I have Docker CE installed on two machines: * my workstation running OpenSUSE Leap 15.1 * a public sandbox server running CentOS 7 I'm currently fiddling with custom networks and container isolation, and it looks like I discovered a bug or at least an inconsistency in CentOS. Maybe the gurus among you have an explanation for this. Sorry if this is a bit long, but I try to be as clear as possible. OpenSUSE Leap 15.1 -- For demonstration purposes on how things *should* be, I'm starting two Nginx containers named "webserver1" and "webserver2": $ docker run -dit --name webserver1 nginx $ docker run -dit --name webserver2 nginx These two containers have the respective 172.17.0.2 and 172.17.0.3 IP addresses: $ docker network inspect bridge | grep -i ipv4address "IPv4Address": "172.17.0.2/16", "IPv4Address": "172.17.0.3/16", The "webserver1" container has the 172.17.0.2 IP address: $ docker exec -it webserver1 hostname -I 172.17.0.2 Since "webserver1" and "webserver2" are both on the "bridge" network, they can communicate with each other: $ docker exec -it webserver1 curl -m 5 http://172.17.0.3 Welcome to nginx! ... Now I'm creating the custom "blog" network: $ docker network create blog $ docker network ls NETWORK ID NAMEDRIVER SCOPE e02e6fc654c6blogbridge local 3ea6f28134babridge bridge local 8d2b8dfe5352hosthostlocal 0bd337e274c2nonenulllocal I'm starting a third container named "webserver3" and assign it to the new "blog" network: $ docker run -dit --name webserver3 --network blog nginx This new container is in a whole new network segment: $ docker network inspect blog | grep -i ipv4address "IPv4Address": "172.20.0.2/16", As is to be expected, it can't communicate with the other two containers: $ docker exec -it webserver3 curl -m 5 http://172.17.0.2 curl: (28) Connection timed out after 5001 milliseconds $ docker exec -it webserver3 curl -m 5 http://172.17.0.3 curl: (28) Connection timed out after 5001 milliseconds So far so good. CentOS 7 Now let's repeat the exact same experiment on a server running CentOS 7. First, create two containers on the default "bridge" network and check if they can communicate with each other: $ docker run -dit --name webserver1 nginx $ docker run -dit --name webserver2 nginx $ docker network inspect bridge | grep -i ipv4address "IPv4Address": "172.17.0.3/16", "IPv4Address": "172.17.0.2/16", $ docker exec -it webserver1 hostname -I 172.17.0.2 $ docker exec -it webserver1 curl -m 5 http://172.17.0.3 Welcome to nginx! ... Now create a custom "blog" network and start a third container assigned to that network: $ docker network create blog $ docker network ls | grep blog 0571c80fef1b blog bridge local $ docker run -dit --name webserver3 --network blog nginx $ docker network inspect blog | grep -i ipv4address "IPv4Address": "172.19.0.2/16", $ docker exec -it webserver3 hostname -I 172.19.0.2 Now IN THEORY "webserver3" shouldn't be able to communicate with the "webserver1" and "webserver2" containers. But here's what happens IN PRACTICE (and only on CentOS 7): $ docker exec -it webserver3 curl -m 5 http://172.17.0.2 Welcome to nginx! ... $ docker exec -it webserver3 curl -m 5 http://172.17.0.3 Welcome to nginx! ... As far as I'm concerned, it looks like a bug, it walks like a bug and it quacks like a bug. Any remarks and/or suggestions? Cheers from the sunny South of France, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : i...@microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Docker container isolation not working in CentOS 7
Le 10/08/2020 à 15:10, Nicolas Kovacs a écrit : > Now IN THEORY "webserver3" shouldn't be able to communicate with the > "webserver1" and "webserver2" containers. > > But here's what happens IN PRACTICE (and only on CentOS 7): > > $ docker exec -it webserver3 curl -m 5 http://172.17.0.2 > > > > Welcome to nginx! > ... > $ docker exec -it webserver3 curl -m 5 http://172.17.0.3 > > > > Welcome to nginx! > ... > > > As far as I'm concerned, it looks like a bug, it walks like a bug and it > quacks > like a bug. I've experimented some more, and while this is clearly a bug, the simple and pragmatic workaround consists in creating a custom network for every container group I want to isolate. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : i...@microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Docker container isolation not working in CentOS 7
On 2020-08-10 15:10, Nicolas Kovacs wrote: Hi, I've decided to use these summer holidays to wrap my head around Docker and its quirks. Spent the last couple weeks working through a Udemy tutorial and a thick book about Docker, and I have Docker CE installed on two machines: Where is your docker coming from? Regards. -- Roberto Ragusamail at robertoragusa.it ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Docker container isolation not working in CentOS 7
Le 10/08/2020 à 17:03, Roberto Ragusa a écrit : > Where is your docker coming from? From the CentOS repository on Docker.com: $ head -n 7 /etc/yum.repos.d/docker-ce.repo [docker-ce-stable] name=Docker CE Stable - $basearch baseurl=https://download.docker.com/linux/centos/7/$basearch/stable enabled=1 gpgcheck=1 gpgkey=https://download.docker.com/linux/centos/gpg Nearly all the online tutorials and Docker documentation strongly suggest to install Docker CE from this source. -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : i...@microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS8 pxeboot Error setting up software source
Folks, Last month i have setup PXE server using CentOS8-1-1911 release and everything was working fine so today i thought let me upgrade it to CentOS8-2-2004 so i just did rsync and updated all packages but after that it started throwing following error during pxe installation Installation source (Error setting up software source) I have check logs and i can see its setting correct source which is my apache server also networking looks good. I can ping server from a kickstart client, i have tried to give multiple repo manually but still have the same error. I am using this repo, let me know if this is wrong place http://mirror.liquidtelecom.com/centos/8.1.1911/BaseOS/x86_64/os/ Is this a bug or something which i am not aware of? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
