I have a CodeReddy Red Hat OpenShift Container platform cluster running on Windows 10.
I have docker image hosted in docker hub (public). When I try to create a Pod using this docker hub hosted image, it's failing om image download.
What could be possible reason?
Internal error occurred: docker.io/ajmaly/public:latest: Get "https://registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io on 10.217.4.10:53: server misbehaving
The output for Resolve-DnsName registry-1.docker.io is below,
Looks like the DNS configuration wasn't setuped properly.
5.1. DNS configuration details
The registry-1.docker.io resolves here to this IP's
dig +short registry-1.docker.io
34.238.187.50
54.224.119.26
34.231.251.252
107.23.149.57
3.224.96.239
3.229.227.53
18.213.137.78
3.220.36.210
Maybe this link could help you to fix your issue.
Installing CodeReady Containers (OpenShift4) on Hyper-V (Win 10)
Related
I have a dedicated server running Ubuntu and Rancher Desktop.
I'd like to be able to access the Kubernetes cluster (K3S) from another computer in the same network.
In doing so, after I've setup my kube configuration, I'm getting an error.
Unable to connect to the server: x509: certificate is valid for 10.43.0.1, 127.0.0.1, 192.168.5.15, ::1, fec0::5055:55ff:fe8e:47db, not 192.168.1.8
Passing the following config through to K3S should solve my problem
INSTALL_K3S_EXEC="--tls-san 192.168.1.8"
Reading through Rancher Desktop documentation, I found a potential solution.
Based on the documentation I should be able to pass config through to k3s via the Provisional Script for Rancher Desktop. It is still unclear to me as how I do this for the K3S configurations.
The k3s repository has this issue with a proposed solution at https://github.com/k3s-io/k3s/issues/3369
"SANs should be added to the dynamiclistener cert on demand, based on the SNI hostname requested by the client. Try running the following on the server:"
curl -vk --resolve 172.31.13.97:6443:127.0.0.1 https://172.31.13.97:6443/ping
I am getting the connection time out when running the command in bootstrap.
Any configuration suggestions on networking part if I am missing
It’s says kubernetes api calling time out
This is obviously very hard to debug without having access to your environment. Some tips to debug the OKD installation:
Before starting the installation, make sure your environment meets all the prerequisites. Often, the problem lies with a faulty DNS / DHCP / networking setup. Potentially deploy a separate VM into the network to check if everything works as expected.
The bootstrap node and the Master Nodes are deployed with the SSH key you specify, so in vCenter, get the IP of the machines that are already deployed and use SSH to connect to them. Once on the machine, use sudo crictl ps and sudo crictl logs <container-id> to review the logs for the running containers, focussing on the components:
kube-apiserver
etcd
machine-controller
In your case, the API is not coming up, so reviewing the logs of the above components will likely show the root cause.
Whenever I try to login to Openshift through CLI I get the following error.
error: dial tcp: lookup api.rhocp1.xxx.com on xxx.xxx.225.1:53: no such host - verify you have provided the correct host and port and that the server is currently running.
But from windows it works absolutely fine. Strange.
Any help is appreciated.
I recently deployed an instance of Ubuntu 16.04 on FIWARE Lab and accessed it using putty, I downloaded docker & docker-compose, I successfully installed fiware-orion & mongo-db as I followed the tutorial, I tried to follow the iot sensor tutorial but whenever I try to start the service it keeps stucking in this infinte loop -> Context Broker HTTP state : 000 (waiting for 200).
Any suggestions?
Details
region:crete
image: ubuntu 16.04
putty infinite loop
The problem was that the docker-compose did not include Orion (and MongoDB) instance which are required dependencies for this tutorial. We have updated the corresponding docker-compose file in order to include both dependencies and now it is working properly. Tips: do not forget to open the corresponding port (3000) in the security and assign a floating IP to the virtual machine to access to the /device/monitor (do not use localhost for accessing it).
Question: How do I get CDK to work on the corporate laptop using virtualbox without running into the 'could not find mathcing ip for mac' issue?
environment: Windows7, CDK 3.2.0, Virtualbox 5.0.x/5.1.x various versions tried. Key callout, corporate machine has VPN software (cisco anyconnect) while home pc does not, home pc works fine. Issue happens regardless if using VPN or not. Virtualbox (all versions) proven to work using vagrant.
Key finding:
minishift ssh -> functions, doing an ifconfig returns eth0 with a 10.0.*
network, instead of the expected 192.168.99.* network segments configured
for virtualbox network host adapters. Explicitly using minishift config set
host-only-cidr 192.168.99.1/24 with matching virtualbox host adapters
doesn't change outcome
Details:
c:\devrh\cdk\bin>minishift version
minishift v1.7.0+204ce19 CDK v3.2.0-1
c:\devrh\cdk\bin>minishift start --vm-driver=virtualbox -- Starting local
OpenShift cluster using 'virtualbox'
hypervisor ... -- Starting Minishift VM ............................ FAIL
E1108 10:27:05.991687 3128 start.go:356] Error starting the VM: Error
configuring authorization on host: Could not find matching IP for MAC
address 0800279fa156. Retrying. Error starting
the VM: Error configuring authorization on host: Could not find matching IP
for MAC address 0800279fa156
corporate workstation has the issue, home PC does not.
Minishift delete and restart, same issue (different MAC address, but same issue).
Virtualbox remove all host adapters, minishift delete, restart (which auto-creates new host adapters), same issue.
Minishift --profile approach, same issue.
Uninstalled virtualbox, installed the version from the RHDevSuite installer with the CDK from the installer, all steps tested with that combination as well, same issue.
Additional notes, Virtualbox is working fine with vagrant (static IP’s in vagrant files), virtualbox/vagrant combo works on both corporate and home machine without issues.