I tried to install hono for test purpose, i tried k8s ( minikube and non -minikube). It didn't work for me by now. I am looking for other alternatives. For example, can I start honor using docker compose ? I checked Ditto that it can be started using docker compose.
#Vigkam , I saw one your message, you had installed hono in one machine. Did you use k8s ?
Thanks
Related
custom:
pythonRequirements:
dockerizePip: true
in Python lambda using serverless with dockerizePip , I'm getting this message.
I know dockerizePip uses docker and it works fine in the local. But, when using it via pipeline, the container it uses to build doesn't seem to have 'docker' there.
Or, Maybe it's there but not running? I get this error message.
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Should I use ECR when I use dockerizePip : true?
Is there a way to not use ECR?
You don't need to use ECR, but docker daemon has to be running on the machine. Docker container will be launched to actually build your dependencies with serverless-python-requirements plugin. You can also try specifying dockerizePip: non-linux, as it might not be needed to dockerize packaging when running on linux machine, but I would advise to test it first on non-prod environment.
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
I have a windows service that I want to run in a docker container on Azure.
I would like to have the same setup when running the service locally, so I would like to run the same docker container locally as a windows service (I think?).
How would I do that? Or is there a better approach?
Thanks,
Michael
IMHO Michael asked how to start docker images without the need to have a user logged in. The docker restart flag actually only deals with starting images after docker is running. To get docker to run without logged in user (or after automatic windows updates) it seems to me you will also need to make a windows service that runs docker.
A good explanation for this part of the problem can be found here (no good solution has been found yet without paying for it - docker team ignored request to make this work without third party so far):
How to start Docker daemon (windows service) at startup without the need to log-in?
You can use the flag --restart=unless-stopped with the docker run command and the docker container will run automatically even if the server was shutdown.
Further read for the restart policy and flag here
but conditions apply - docker itself should always run on startup. which is default setting by itself.
Is it possible to set up JHipster console on Docker Cloud? My application is deployed on Heroku.
If is there no option, please advise where can I set up docker in cloud.
Regards!
Yes docker cloud is an option although I've never tried it. If you have simple needs and don't need container orchestration on multiple hosts I would recommend creating a simple VM with docker on your favorite cloud provider (using docker-machine for example) and then deploy the console there using docker-compose. It's really easy to do.
1) SSH on your server
2) Install docker and docker-compose
3) Get the docker-compose file from https://github.com/jhipster/jhipster-console/blob/master/bootstrap/docker-compose.yml
4) Run docker-compose up -d
The console will be available on port 5601.
Refer to the docs at : https://jhipster.github.io/monitoring/
More advanced setup are possible but this is the easiest way to go. Also note that it is perfectly possible to run the JHipster-Console without Docker but it requires some work. To do this, setup an ELK stack yourself usinh on simple logstash configuration and scripts to preload the dashboards.
Ok, locally everything is fine. So how (step by step) push JHipster Console to docker-cloud and connect it with my application on heroku?
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.