i need some help for installing kyma locally.
I was following the official guide:
https://kyma-project.io/docs/kyma/latest/04-operation-guides/operations/02-install-kyma/
I have:
Windows 10
Hyper-V activated
Docker Desktop installed (v4.9.1)
Kubernetes (1.24.0) - shown by kubectl version --client
K3d (v5.4.3)
kyma-cli 2.0.4
kubernetes-helm 3.8.2
I installed it like this:
Starting up Docker Desktop
kyma provision k3d
kyma deploy
While deploying now, i get some errors, which tell me, that some essential components can not be deployed:
Errors
Can you help me solve this so that i can start up a functional kyma instance?
Greetings and thanks in advance!
The issue was the kubernetes version. After downgrading my docker desktop to 4.1, which is using kubernetes 1.21 it works now.
As of version 1.20, Kubernetes deprecated Docker as a container runtime in favor of containerd. Due to a different way in which containerd handles certificate authorities, Kyma's built-in Docker registry does not work correctly on clusters running with a self-signed TLS certificate on top of Kubernetes installation where containerd is used as a container runtime.
If that is your case, either upgrade the cluster to use Docker instead of containerd, generate a valid TLS certificate for your Kyma instance or configure an external Docker registry.
another way is to disable kubernetes provided by docker-desktop and use the command below to provision kubernetes cluster based on k3d
kyma provision k3d
Related
I have an already existing docker image that is linux/arm64 because i have an m1 mac, but I want to host it on azure.
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"WebhookInvalidParameterValue","message":"The following field(s) are either invalid or missing. Invalid value: "myregistry.azurecr.io/myproject:latest": image OS/Arc must be linux/amd64 but found linux/arm64: template.containers.myproject.image."}]}
Is it a way to host the existing image on azure or convert it to linux/amd64?
Currently, Azure Container Apps only support Linux-based x86-64 (linux/amd64) container images so you can't deploy an ARM-based container. Documentation
On a M1 Mac, you can build multiarch containers using Buildx. This way, you can build an x86-64 version of your container that you'll be able to deploy on Container Apps. Documentation
You can also build the container image using your Azure Container Registry, instead of building it locally using cross-compile. ACR can build it for amd64.
https://learn.microsoft.com/en-us/cli/azure/acr?view=azure-cli-latest#az-acr-build
I have a problem on a running Hyperledger Fabric network 1.4 that was working OK on Azure Kubernetes 1.17 after migrating to 1.19.
The chaincode is no longer working and peer nodes shows error "cannot connect to Docker endpoint".
Looks like the connection between the peer nodes and the DinD daemon is dead now (I was using unix:///host/var/run/docker.sock ) as CORE_VM_ENDPOINT.
Is there any workaround? Maybe there is a way to go back to tcp://docker:2375 for the CORE_VM_ENDPOINT value?
Thanks
AKS changed the container runtime from Docker to containerd some time ago. This is why the Docker socket isn't available anymore.
In September 2021 the Ubuntu 18.04 node images when GA. With those containerd got introduced. These node images are the default images when using or upgrading to Kubernetes 1.18.
Some more details:
containerd and AKS
Ubuntu 18.04 node image
I am currently trying to start ElasticSearch on an Azure app service using Docker. I install docker through the ssh available in azure app services. Docker seem to install alright in the console, however when I run
docker pull docker.elastic.co/elasticsearch/elasticsearch:7.6.2
I get the following error in the ssh console:
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
I have installed and uninstall Docker several times, however I still get the same error
Azure App service does not allow you to run Elastic Search due to its limitations
You may use Elastic as a Service on Azure or install it in AKS or VM.
https://azuremarketplace.microsoft.com/en-us/marketplace/apps/elastic.ec-azure?tab=Overview
You are trying to install Docker inside the Docker container
App Service for Linux comes with a bunch of preconfigured containers such as Node, PHP, Java, Python, Ruby and .NET Core.
https://anthonychu.ca/post/jekyll-azure-app-service-linux/
The exact issue you mentioned means that Docker daemon is not started in your Linux environment
To start the Docker daemon use command:
systemctl start docker
I'm trying to install kubernetes on one of my centos host using kubeadm. But in the same host, there is already running microservices multicontainer application. When i enable the firewalld service while installing kubernetes to allow the ips which are required to the kubernetes, my docker multicontaier application is flushing off its connections. Could anyone please help me to install kubernetes on the same host while my docker application running smooth ? I've tried sequentially starting the applications such as starting docker demon after the firewalld and vice versa but it also not working.
I've done this by switching off the firewalld and letting kubern8s to choose its own ports.
can someone help with how to deploy wso2esb in docker container with kubernetes?
currently im running only one node/master at local machine with ubuntu server 14.04 LTS
if im running with this
sudo docker run --name esb isim/wso2esb
it instantly trigger the service inside the container
but if im running with this
kubectl run esb1 --image=isim/wso2esb
the container just run, without trigger the service inside the container
btw im using isim/wso2esb from docker hub
hope someone can help me..
From the comments above, it looks like you were connecting to the wrong IP address, which you discovered by running kubectl logs esb1.
In general, you can follow the Kubernetes Debugging FAQ when you see an issue like this to see if it is a common problem that has already been documented.