Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed last month.
Improve this question
I am currently getting familiar with Docker and one issue I have is launching several Docker containers on the same host machine.
If I run 32 or less containers, everything works fine.
However, if I start more containers, not only my host machine loses internet connection, but also the containers are not able anymore to communicate with each other.
After searching the web, this seems to be a common issue, but no solution worked for me yet.
I tried setting up custom Docker network bridges as well as editing the /etc/docker/daemon.json file.
In any case, if I run docker network inspect on the respective network, everything seems fine and each containers has its own IP address correctly assigned.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
As we all know newest versions of k8s coming with container-d run time , in previous versions I was able to run container inside container (pod) , by using docker in docker approach,
How can I achieve this functionality now.
Docker should works in Kubernetes v1.19 as usually (also Docker in Docker), because:
Kubernetes is deprecating Docker as a container runtime after v1.20.
and:
Dockershim is being removed from Kubelet as early as v1.23 release,
which removes support for Docker as a container runtime as a result.
In that case you need to change your container runtime from Docker to another supported container runtime.
One thing to note: If you are relying on the underlying docker socket
(/var/run/docker.sock) as part of a workflow within your cluster
today, moving to a different runtime will break your ability to use
it. This pattern is often called Docker in Docker. There are lots of
options out there for this specific use case including things like
kaniko,
img, and
buildah.
More information on the official Kubernetes page
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I have a cluster on GKE currently on version v1.19.9-gke.1400. Accordingly do kubernetes release notes, on 1.20 dockershim will be deprecated. My cluster is configured to auto-upgrades and in one specific application I use docker socket mapped to the application, where I run direct containers through their API.
My question: In a hypothetical upgrade of the cluster to the 1.20 version of kubernetes, the docker socket will be unavailable immediately? Or the deprecated flag only points that in the future it will be removed?
Yes, if you use the non-containerd images. In the node pool config you can choose which image type you want and COS vs COS_Containerd are separate choices there. At some point later in 2021 we may (if all goes according to plan) remove Docker support in Kubernetes itself for 1.23. However Google may choose to remove support one version earlier in 1.22 or continue it later via the out-of-tree Docker CRI that Mirantis is working on.
I am running 1.20 in the Rapid channel and can confirm that Docker is still there and happy. Also FWIW if you need to run dockerd yourself via a DaemonSet it takes like 30 seconds to set up, really not a huge deal either way.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I have a private insecure registry on an Ubuntu Server 18.04 (using docker-compose), whose IP is let's say 192.168.168.168; when on a Windows client I browse from Chrome to
http://192.168.168.168:5000/v2/_catalog
I get
{"repositories":["hello-world2","mywebservice"]}
which is ok, since I pushed them to the private registry.
However, if I run
docker image list
on the server, only "hello-world2" is shown. There's no "mywebservice" entry.
How is that possible?
As far as I understand, a registry is a separate entity which has no direct relationship with the Docker client possibly installed on the same server where the registry is.
In other words, if I push an image from a Docker client on machine A to the registry on machine B, any Docker client on machine B won't get that image unless it explicitly pulls that image from the registry, even if the registry is on the same machine B.
In my case I didn't pull the "mywebservice" image from the registry to the client, both on machine B.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I have a private insecure registry on an Ubuntu Server 18.04 (using docker-compose), whose IP is let's say 192.168.168.168; when on a Windows client I browse from Chrome to
http://192.168.168.168:5000/v2/_catalog
I get
{"repositories":["hello-world2","mywebservice"]}
which is ok, since I pushed them to the private registry.
So:
How do I run those images on the Ubuntu server?
With regard to the "mywebservice", which is a REST webservice, how do I run it, so I can access it from a browser of my local Windows client?
I already tried
docker run 192.168.168.168:5000/mywebservice
but got
Unable to find image '192.168.168.168:5000/mywebservice:latest'
locally
A Docker registry is not a Docker Engine and it cannot run containers.
If one wants to run a Docker container on the same server where the Docker registry is, it is necessary to pull the image from the registry to a Docker client (using docker pull localhost:5000/image_name), and then run it the usual way.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
I want to create a docker container which contains one or more containers.
Is it possible with Docker?
To run docker inside docker is definitely possible. The main thing is that you run the outer container with extra privileges (starting with --privileged=true) and then install docker in that container.
Check this blog post for more info: Docker-in-Docker.
One potential use case for this is described in this entry. The blog describes how to build docker containers within a Jenkins docker container.
However, Docker inside Docker it is not the recommended approach to solve this type of problems. Instead, the recommended approach is to create "sibling" containers as described in this post