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 4 years ago.
Improve this question
On Windows, I've always been able to build Docker images with no problems.
I'm now trying to build a simple Docker image on Ubuntu 18.04 and typing in the terminal:
sudo docker build -t test .
results in the following error:
Cannot connect to the Docker daemon at unix:///var/run/docker.sock.
Is the docker daemon running?
How do I start the Docker daemon? I want to be able to build the image successfully
EDIT:
Typing sudo systemctl start docker as stated in the original documentation https://docs.docker.com/config/daemon/systemd/ results in the following error:
Failed to start docker.service: Unit docker.service is masked.
You can configure docker to start on boot :
sudo systemctl enable docker
The ugly way : start docker manually :
dockerd &
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 8 months ago.
Improve this question
I am using docker with k8s from mac terminal. Don't know what I have done, my docker command does not work anymore. For example, docker info and docker run... hang forever. I've tried to fix this problem by uninstalling and installing docker. But after I reinstalled docker, I got this error message:
> $ docker info Client: Context: default Debug Mode: false
>
> Server: ERROR: Cannot connect to the Docker daemon at
> unix:///var/run/docker.sock. Is the docker daemon running? errors
> pretty printing info
For other docker commands, I also received:
ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
errors pretty printing info
I've read through lots of websites (How to easily install and uninstall docker on MacOs) ("VirtualBox is configured with multiple host-only adapters with the same IP" when starting docker)..., but still unable to fix my problem. A lot of solutions do not seem to work on macos. I've seen many solved by the systemctl command, and I tried to replace that with launchctl and followed the rest of the instructions. (Cannot connect to the Docker daemon at unix:/var/run/docker.sock. Is the docker daemon running?) But none works for me.
Please help solve this problem. Thank you!
I just found out that I have to restart my docker desktop as well. I had no idea that docker desktop and terminal's docker command are related. But now, apparently, they are related. If anyone encounters similar problems, remember to try restart your docker desktop and wait for it to get running!
chown root:docker /var/run/docker.sock
chmod g+w /var/run/docker.sock
Try to give/Modify Permission.
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've installed GitLab ee on Docker. I'd like to use authentication via ssh instead password but each time I try to authenticate, connection is closed. SSH Port is 1122->22 so I'm connecting with git#gitlab.example -p 1122. I also enabled the port in ufw, checked if openssh server is running in the container.
Error: Connection closed by HOST port 1122
I was searching long time but I didn't find anything so I'll be glad for any suggestion.
Potential problem with Docker and UFW
Time ago I was wondering how to work with both UFW and Docker together (The GitLab service doesn't seem to be the problem, pretty sure you could have had the same problems with any service at all).
Check out this thread: What is the best practice of docker + ufw under Ubuntu
And also consider this:
To persist the iptables rule install the linux package iptables-persistent according to your server distro, in my case (Debian) is sudo apt install iptables-persistent and the package installation will add the NAT rule to a persistent file which is executed on boot. ~afboteros
Potential problem with Gitlab and Docker
When using Gitlab through Docker, some "heavy port-binded" services like SSH might need you to configure them to the exposed port. Maybe if you set the SSH service to the 1122 as you intended to, and binding it like that on the Dockerfile maybe you could make it work.
Official Gitlab documentation
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 am trying to add private registry in docker on ubuntu machine, using nexus as repository
below is the screenshot of nexus configurations
in docker host i have added DOCKER_OPTS="--insecure-registry=xx.xx.xx.xx:8083" to /etc/default/docker
after these changes i did docker restart using below commands
systemctl daemon-reload
systemctl restart docker
now when i execute docker info its not showing up my private registry
is anything missing in my configurations
Try adding insecure registry entry in /etc/docker/daemon.json
file content
{ "insecure-registries":["registry.example.com"] }
restart the docker deamon
sudo systemctl restart docker
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
I bought a server for experimenting with docker. Now I need an OS, that docker can run on it. Which OS would you recommended to me? CoreOs, RancherOS, etc.
How about service discovery?
I want to run my microservices on container, that is my target.
Docker is compatible with Linux, Mac OS X, or Windows. I will prefer Linux as in Linux your machine will act as a localhost and the Docker host, in networking, localhost means your computer and the Docker client, the Docker daemon, and any containers run directly on your localhost while in Windows the docker daemon is running inside a Linux virtual machine. You will use the Windows Docker client to talk to the Docker host VM. Your Docker containers run inside this host.
Docker on Windows
Docker on Linux
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I am trying to shutdown a kvm on a centos using virsh shutdown vm1 command. I checked to see if the ACPI feature is present in the specification xml using virsh dumpxml vm1 | grep -F acpi and it is. What am I missing here? I don't want to force shutdown the vm.
The acpid daemon process must be running in the VM guest or it will not respond to the request from the hypervisor.
From inside the guest:
service acpid status
should return the running acpid. If it does not try:
sudo yum install acpid
sudo chkconfig acpid on
sudo service acpid start