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 need add to my docker network which I using for squid, outgoing ip range from xx.ip to yy.ip.
At the moment I adding single ip using bellow command:
iptables -t nat -A POSTROUTING -s 172.18.0.0/16 ! -o bridge-coi -j SNAT --to-source 1xx.xxx.xxx.xx4
How I can add range ip?
When I put several many above command, not working.
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.
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
Using gcloud compute engine to run several interconnected services
IPFS node (glcoud compute engine)
Postgres database (gcloud SQL)
Nginx + Docker app (gcloud compute engine)
In attempting to forward and open correct ports for service interconnectivity, I found some issues. Specifically when opening ports for non web or non ssh ports, and/or listening to non-standard web ports using NginX (eg. for forwarding of http requests on non-standard ports to the docker container).
Using Nmap, I discovered over 900 ports are in 'filtered' state. I'm assuming because Google cloud virtual hosting is using bc.googleusercontent.com as primary host.
This is an example: Port 8020 is being filtered as 'intu-ec-svcdisc' service. I found it to be this service INTUIT service discoverer.
I'm hoping to discover a way to open several of these ports that I need.
As per nmap
Filtered means that a firewall, filter, or other network obstacle is blocking the port so that Nmap cannot tell whether it is open or closed. Closed ports have no application listening on them, though they could open up at any time.
By default, GCP only allows port 22/tcp & 3389/tcp incoming traffic to all your instances, however you have the option to tag your GCE resourse with http-server and/or https-server to allow ports 80/tcp & 443/tcp as well.
What you are seeing on your nmap output is exactly those ports open / closed because those can actually reach your GCE instance, but GCP firewall is blocking additional incoming traffic by default, and therefore you see this as "filtered".
You would need to open your desired ports on here by using the following guide or video, keep in mind that you can also have enabled a firewall inside your operating system, that could be turning those requests away.
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.
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 &