I started to learn Skaffold (https://codelabs.developers.google.com/skaffold-deep-dive#2).
Now I ran got stuck trying his examples (https://github.com/GoogleContainerTools/skaffold/tree/main/examples/microservices).
After I ran microservices example I discovered 2 containers left, except minikube:
If I try to delete them, they restart 😠.
I start to investigate:
Until now I didn't find any decent solution, except reinstalling Docker Desktop, which is ugly 😕.
Can you help me with this ? Pleeease !
Related
My Kubernetes cluster on docker for desktop on Mac is non responsive.
So I tried to reset Kubernetes as was suggested in
delete kubernetes cluster on docker-for-desktop OSX
The results are:
All Kubernetes resources are deleted
Kubernetes restart hangs
GUI to disable Kubernetes is grayed out and non responsive
I would like to avoid reseting docker so I can keep my image repository
How do I manually remove Kubernetes from docker VM?
You can try disabling Docker Kubernetes in the settings file. You can find settings file in path ~/Library/Group\ Containers/group.com.docker/settings.json. Edit kubernetesEnabled property to false.
"kubernetesEnabled" : false,
I have ended up in situation where k8s is partly deleted and was not able to start docker. Restarting and/or changing this setting helped and did not delete images. I was not able to reproduce the situation later.
Also make sure you are running latest version of Docker.
How about this?
‚docker rm -f $(docker ps -aq)‘
This deletes and removes all containers.
I can't give you a technical answer that immediately fixes your problem, and this text is too long for a comment... but as someone who also had the same issue (couldn't disable k8s without a factory reset in Docker for Mac), my recommendation is:
Is it really worth for you to keep the image repository? Consider, what's a container? A program. It's not a VM. Would you backup your ls, ssh, vim... binaries when you want to initialize your OS? No right? But this is the same, you should view the container like another binary.
Odds here are that if you mess with manual actions, you will end up with a docker daemon in an undesired state. So, IMO, just go ahead and purge the Docker for Mac and start over, it's not really a big deal.
If you have tons of own images, you can build them right away. If you have tons of downloaded images, consider this as a good thing to do some cleaning. Also, notice that images work in layers, so if your images are correctly build leveraging the use of layers, the building process will be quite fast.
To remove the kuberntes cluster from docker desktop you need to run: rm -rf ~/.kube
I simply cannot find a solution for this " Unable to connect to the server eof", hopefully we solve this and it helps somebody in future, when searching to fix this issue. I tried to include all information in the screenshot. Let me know if more information is required.
I have tried to add the information requested, let me know if theres anything else you need or want me to try.
Please try to get into logs of kube-dns docker container directly as below:
Enable 'Show system containers' option in Docker Desktop settings:
Check if kube-dns container was ever run:
docker ps -a --filter name=k8s_kubedns_kube-dns --format "table
{{.ID}}\t{{.Image}}"
You should see similar command output to this:
CONTAINER ID IMAGE 9009731e183d 80cc5ea4b547
Get kube-dns container logs with:
docker logs {your_container_id} --tail 100
I had this error (with Docker Desktop on Windows 11, using wsl2), and the solution for me was to use the Settings page (in DD), then choose "Kubernetes" on the left, then chose "reset kubernetes cluster". That warned that all stacks and k8s resources would be deleted, but as nothing else had worked for me (and I wasn't worry about losing much), I tried it, and it did solve the problem.
FWIW, k8s had been working fine for me for some time. It was just that one day I found I was getting this error. I searched and searched and found lots of folks asking about it but not getting answers, let alone this answer (even here). To be clear, I had tried restarting Docker Desktop, restarting the host machine, even downloading and installing an available DD update (I was only a bit behind), and nothing worked. But the reset did.
I realize some may fear losing something, but again it worked and was worth it for me. Hope that may help others.
I am using Docker 1.8.2c, VirtualBox 5.0.4 on Windows 8.1.
I have been successfully been using this configuration for a long period, but then I had to install OpenShift to check its feasibility. This never worked out as there were networking issues with new network adapters being created all the time, and not being able to connect to the internet.
I have uninstalled everything, and reinstalled Docker 1.8.2c and somehow the problem is still persistent and Docker will not even start now.
I have looked around and not found a way to investigate or resolve the problem.
Thanks for your advice.
Cheers
Kris
Try to do an upgrade like Dan Lowe said and if you have error messages can you post them here ?
This is incredibly strange to me. Neo4j won't start a second time unless I restart Windows.
I installed neo4j Community Edition 3.0.3 on 64-bit Windows 7 and followed this youtube tutorial https://www.youtube.com/watch?v=Foj2tzq84DY. The tutorial was embedded in neo4j's site https://neo4j.com/download-thanks/?edition=community&flavour=winstall64&release=3.0.3&_ga=1.203356307.385208157.1468345542. Even thought the video lists 2.3 it's linked by Neo4j 3.0.3 download and worked fine for 3.0.3.
Everything worked like a charm. I played around with it for a while and things worked fine. I then shut it down, by clicking on stop in the little gui launcher. When I tried to start it up again, through the start menu, nothing seems to happen at all. I went into the Neo4j CE 3.0.3\bin directory and tried running from there, but I see no error messages, no log directory, no error dialog. I just seems to do nothing. I've also tried "neo4j-ce.exe start" and "neo4j-ce.exe restart". Nothing seems to work.
I checked windows services and didn't see any services starting with neo4j. Don't know if default setup runs it as a service, but if so, maybe it's under something else?
I have been able to get things to start up if I restart Windows, but that's a royal pain and cannot imagine that's intentional.
I do see that there's a jar in the bin directory, so I imagine I could start it with a java command, but I don't know the specifics. However, it's most disconcerting that there is no error message at all. I imagine that something didn't shut down properly, but at this point I have no idea what might be going wrong.
Any help is greatly appreciated.
I don't know if this is a bug with the launcher for the community edition of neo4j on windows 7 or not, but what I've found is that when you close the launcher dialog, it does not kill the neo4j-ce process. Thus, since the process is already running, albeit in a stopped state, it won't start again. The challenge there is, of course, that the dialog is gone and you can't click the start button to essentially connect to a database.
The solution is to go into Task Manager and end the "neo4j-ce.exe" process.
Once that is done you can start Neo4j normally.
I wanted to know if it is possible to keep an eye on postgreSQL using supervisor on a debian server? I haven't been able to find any examples, so I am wondering if it is worth it, or perhaps there is a more straight forward way of ensuring it is always running.
See Using PostgreSQL with Supervisor on Ubuntu 10.10 and the clarifications at Running PostgreSQL with Supervisord. There are some useful examples in a pastebin too. Given the common name of the program it can be hard to find these, the trick to getting examples is to search for supervisord instead.