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
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
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 2 years ago.
Improve this question
unable to login or pull images from docker hub, from windows docker for desktop
I get the below error,
Error response from daemon: Get https://foo.bar.com/v2/: dial tcp 10.1.20.64:443: connect: no route to host
Try to remove the other bridged network other than the default one and try to pull the image again and it worked for me.
> docker network ls
NETWORK ID NAME DRIVER SCOPE
b139fe9f89e3 bridge bridge local
e5dfbbee314v network-1 bridge local
6ruvy84eg56n network-2 bridge local
1e0ccbec292a host host local
e1c69bce4r56 none null local
> docker network rm e5 6r
> docker pull private-repo:port-number/your/image:latest
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 3 years ago.
Improve this question
I would like to know how to create a docker private registry in EC2 Instance?
Thanks in advance.
You should consider using managed solutions for docker registry to ensure scalability and availability like ECR, Dockerhub or Quay.io
However, if you still want to have your own private registry in EC2, here are the steps for the simplest setup:
Install docker inside the EC2. If you use AWS Linux AMI then docker is already installed.
Create a local directory to persist registry data
mkdir -p /opt/registry
Run the following command to spin up a private registry
docker run -d \
-p 5000:5000 \
--restart=always \
--name registry \
-v /opt/registry:/var/lib/registry \
registry:2
Update the security group for EC2 so that the registry can be accessed from outside at port 5000
Reference: Docker documentations
Note: There are a lot of things to consider before bringing your private registry to production like: security (encrypting traffic at rest and in transit), high-availability (what if the EC2 is being shut-down for any reason), etc.
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 &
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