sles

问题 I try to install Kuberneties cluster on SLES. But When I do Kubeadm init using below command it gives given error. Kubeadm init kubeadm init --pod-network-cidr=10.244.0.0/16 --kubernetes-version=1.15.3 Error error execution phase preflight: [preflight] Some fatal errors occurred: [ERROR SystemVerification]: unsupported graph driver: btrfs [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...` In SLES default file system is btrfs. So as

问题 I try to install Kuberneties cluster on SLES. But When I do Kubeadm init using below command it gives given error. Kubeadm init kubeadm init --pod-network-cidr=10.244.0.0/16 --kubernetes-version=1.15.3 Error error execution phase preflight: [preflight] Some fatal errors occurred: [ERROR SystemVerification]: unsupported graph driver: btrfs [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...` In SLES default file system is btrfs. So as

问题 I try to install Kuberneties cluster on SLES. But When I do Kubeadm init using below command it gives given error. Kubeadm init kubeadm init --pod-network-cidr=10.244.0.0/16 --kubernetes-version=1.15.3 Error error execution phase preflight: [preflight] Some fatal errors occurred: [ERROR SystemVerification]: unsupported graph driver: btrfs [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...` In SLES default file system is btrfs. So as

问题 I try to install Kuberneties cluster on SLES. But When I do Kubeadm init using below command it gives given error. Kubeadm init kubeadm init --pod-network-cidr=10.244.0.0/16 --kubernetes-version=1.15.3 Error error execution phase preflight: [preflight] Some fatal errors occurred: [ERROR SystemVerification]: unsupported graph driver: btrfs [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...` In SLES default file system is btrfs. So as

问题 I try to install Kuberneties cluster on SLES. But When I do Kubeadm init using below command it gives given error. Kubeadm init kubeadm init --pod-network-cidr=10.244.0.0/16 --kubernetes-version=1.15.3 Error error execution phase preflight: [preflight] Some fatal errors occurred: [ERROR SystemVerification]: unsupported graph driver: btrfs [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...` In SLES default file system is btrfs. So as

问题 I've got a SLES server installed by someone who is not available. I've checked /etc/zypp/repos.d , there is a repo file SUSE-Linux-Enterprise-Server-11-SP4 11.4.4-1.109.repo It's content is : [SUSE-Linux-Enterprise-Server-11-SP4 11.4.4-1.109] name=SUSE-Linux-Enterprise-Server-11-SP4 11.4.4-1.109 enabled=1 autorefresh=0 baseurl=cd:///?devices=/dev/sr0 path=/ type=yast2 keeppackages=0 The CD repository (/dev/sr0) is not available. I would like to add default net repository/repositories to it

问题 I've got a SLES server installed by someone who is not available. I've checked /etc/zypp/repos.d , there is a repo file SUSE-Linux-Enterprise-Server-11-SP4 11.4.4-1.109.repo It's content is : [SUSE-Linux-Enterprise-Server-11-SP4 11.4.4-1.109] name=SUSE-Linux-Enterprise-Server-11-SP4 11.4.4-1.109 enabled=1 autorefresh=0 baseurl=cd:///?devices=/dev/sr0 path=/ type=yast2 keeppackages=0 The CD repository (/dev/sr0) is not available. I would like to add default net repository/repositories to it

问题 I've got a SLES server installed by someone who is not available. I've checked /etc/zypp/repos.d , there is a repo file SUSE-Linux-Enterprise-Server-11-SP4 11.4.4-1.109.repo It's content is : [SUSE-Linux-Enterprise-Server-11-SP4 11.4.4-1.109] name=SUSE-Linux-Enterprise-Server-11-SP4 11.4.4-1.109 enabled=1 autorefresh=0 baseurl=cd:///?devices=/dev/sr0 path=/ type=yast2 keeppackages=0 The CD repository (/dev/sr0) is not available. I would like to add default net repository/repositories to it

来源： https://stackoverflow.com/questions/61589586/opensuse-zypper-error-valid-metadata-not-found-at-specified-url-repository-ty

问题 Our AD Team is going to disable RC4-HMAC so I have to change our JBoss-applications to AES. I added the aes types to krb5.conf and created new keytabs but that seems to not work. Tests besides the application with kinit show the same results. There was an similar issue but its solution was already enabled for us. There is another guy (Rick Moritz) with my problem without an answer. Server: SLES12 AD: Windows Server 2016 krb5.conf [libdefaults] debug = false default_realm = MY.DOMAIN ticket