Skip to main content

Remote Docker Host Using Docker Client

Connecting remote docker host using docker client

In previous post (here) we have seen, by default docker is going to start within host using UNIX socket unix:///var/run/docer.sock. At this time we can only manage docker from the local machine, if we want to accept the connection requests from a remote client we need to start the docker daemon on remote port. So here we are going to setup the remote port.

First we need to stop the existing socket, we can stop it by using the following comamnd:

# systemctl stop docker

Some time socket not get closed by stopping the service, so we can remove the socket manually as well.

# rm -r /var/run/docker.sock


Now we can start it on a specific port by using following command:

# docker -H tcp://0.0.0.0:5050 -H unix:///var/run/docker.sock -d &


Now we can verify it using following command:

# netstat -tupnl | grep 5050


Let's try to access the docker port from the remote client.

# docker -H 10.10.1.186:5050 ps

Here 10.10.1.186 is my docker host ip.

Now also we can create the container using the remote port.

# docker -H 10.10.1.186:5050 run -it –name linux-container ubuntu


We can verify it now using the ls command, because this is the interactive container.

# ls

<=== Previous post about the Linux Container Installation and Configuration ===> 



Comments

Popular posts from this blog

Docker Container Management from Cockpit

Cockpit can manage containers via docker. This functionality is present in the Cockpit docker package. Cockpit communicates with docker via its API via the /var/run/docker.sock unix socket. The docker API is root equivalent, and on a properly configured system, only root can access the docker API. If the currently logged in user is not root then Cockpit will try to escalate the user’s privileges via Polkit or sudo before connecting to the socket. Alternatively, we can create a docker Unix group. Anyone in that docker group can then access the docker API, and gain root privileges on the system. [root@rhel8 ~] #  yum install cockpit-docker    -y  Once the package installed then "containers" section would be added in the dashboard and we can manage the containers and images from the console. We can search or pull an image from docker hub just by searching with the keyword like nginx centos.   Once the Image downloaded we can start a contai

Remote Systems Management With Cockpit

The cockpit is a Red Hat Enterprise Linux web-based interface designed for managing and monitoring your local system, as well as Linux servers located in your network environment. In RHEL 8 Cockpit is the default installation candidate we can just start the service and then can start the management of machines. For RHEL7 or Fedora based machines we can follow steps to install and configure the cockpit.  Following are the few features of cockpit.  Managing services Managing user accounts Managing and monitoring system services Configuring network interfaces and firewall Reviewing system logs Managing virtual machines Creating diagnostic reports Setting kernel dump configuration Configuring SELinux Updating software Managing system subscriptions Installation of cockpit package.  [root@rhel8 ~] #  dnf   install cockpit cockpit-dashboard  -y  We need to enable the socket.  [root@rhel8 ~] #  systemctl enable --now cockpit.socket If firewall is runnin

Containers Without Docker on RHEL/Fedora

Docker is perfectly doing well with the containerization. Since docker uses the Server/Client architecture to run the containers. So, even if I am a client or developer who just wants to create a docker image from Dockerfile I need to start the docker daemon which of course generates some extra overhead on the machine.  Also, a daemon that needs to run on your system, and it needs to run with root privileges which might have certain security implications. Here now the solution is available where we do not need to start the daemon to create the containers. We can create the images and push them any of the repositories and images are fully compatible to run on any of the environment.  Podman is an open-source Linux tool for working with containers. That includes containers in registries such as docker.io and quay.io. let's start with the podman to manage the containers.  Install the package  [root@rhel8 ~] # dnf install podman -y  OR [root@rhel8 ~] # yum