node.js-Nginx docker作为本地的nodejs代理

目前我正在docker中使用Nginx代理我的节点应用程序

例如我在主机文件中添加website.dev

而我实际的nginx配置是

worker_processes 4;
pid /run/nginx.pid;

events {}

http {

    server {
      listen 80;
      server_name website.dev;
      location / {
          proxy_pass    http://localnode:3000;
          proxy_set_header X-Base-Path "/";
          proxy_set_header Website-Name "test";
      }
    }
}

我使用此命令启动我的Docker容器

docker run --name infra-nginx --add-host localnode:$(ifconfig | grep inet | grep -v inet6 | grep -v 127.0.0.1 | awk '{print $2}') -p 80:80 -d docker-registry.host.com:5000/infra-nginx:dev

哪里

$(ifconfig | grep inet | grep -v inet6 | grep -v 127.0.0.1 | awk '{print $2}') is getting my local ip,not working all the time.

问题是,如果我想在没有互联网的情况下工作,那是不可以的.
当我的IP更改时,我必须使用新的IP重新启动容器.

我尝试使用此配置

worker_processes 4;
pid /run/nginx.pid;

events {}

http {

    server {
      listen 80;
      server_name localhost;
      location / {
          return 200 'gangnam style!';
      }
    }

    server {
      listen 80;
      server_name website.dev;
      location / {
          proxy_pass    http://localhost:3000;
          proxy_set_header X-Base-Path "/";
          proxy_set_header Website-Name "test";
      }
    }
}

并运行

docker run --name infra-nginx --network host -d docker-registry.host.com:5000/infra-nginx:dev

在这种情况下,当我跑步时:

curl http://website.dev/

我有

curl: (7) Failed to connect to website.dev port 80: Connection refused

Dockerps给

81da561dd131        ajouve/infra-nginx:dev   "nginx -g 'daemon ..."   32 minutes ago      Up 32 minutes                                                          infra-nginx

netstat -plant给我

Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      1/nginx: master pro
tcp        0      0 172.17.0.1:35962        172.17.0.4:27017        ESTABLISHED -
tcp        0      0 172.17.0.1:35938        172.17.0.4:27017        ESTABLISHED -
tcp        0      0 172.17.0.1:35994        172.17.0.4:27017        ESTABLISHED -
tcp        0      0 172.17.0.1:45080        172.17.0.5:6379         ESTABLISHED -
tcp        0      0 172.17.0.1:35990        172.17.0.4:27017        ESTABLISHED -
tcp        0      0 192.168.65.2:44900      151.101.0.204:80        TIME_WAIT   -
tcp        0      0 172.17.0.1:45126        172.17.0.5:6379         ESTABLISHED -
tcp        0      0 172.17.0.1:36000        172.17.0.4:27017        ESTABLISHED -
tcp        0      0 172.17.0.1:35958        172.17.0.4:27017        ESTABLISHED -
tcp        0      0 172.17.0.1:59172        172.17.0.3:5672         ESTABLISHED -
tcp        0      0 172.17.0.1:35976        172.17.0.4:27017        ESTABLISHED -
tcp        0      0 172.17.0.1:59106        172.17.0.3:5672         ESTABLISHED -
tcp        0      0 172.17.0.1:35980        172.17.0.4:27017        ESTABLISHED -
tcp        0      0 172.17.0.1:35996        172.17.0.4:27017        ESTABLISHED -
tcp        0      0 172.17.0.1:58356        172.17.0.4:27017        ESTABLISHED -
tcp        0      0 172.17.0.1:35966        172.17.0.4:27017        ESTABLISHED -
tcp        0      0 172.17.0.1:45112        172.17.0.5:6379         ESTABLISHED -
tcp        0      0 172.17.0.1:35932        172.17.0.4:27017        ESTABLISHED -
tcp        0      0 172.17.0.1:58366        172.17.0.4:27017        ESTABLISHED -
tcp        0      0 172.17.0.1:35998        172.17.0.4:27017        ESTABLISHED -
tcp        0      0 192.168.65.2:41386      206.251.255.63:80       TIME_WAIT   -
tcp        0      0 172.17.0.1:58358        172.17.0.4:27017        ESTABLISHED -
tcp        0      0 172.17.0.1:35956        172.17.0.4:27017        ESTABLISHED -
tcp        0      0 172.17.0.1:35924        172.17.0.4:27017        ESTABLISHED -
tcp        0      0 172.17.0.1:36004        172.17.0.4:27017        ESTABLISHED -
tcp        0      0 172.17.0.1:58360        172.17.0.4:27017        ESTABLISHED -
tcp        0      0 172.17.0.1:35964        172.17.0.4:27017        ESTABLISHED -
tcp        0      0 172.17.0.1:35916        172.17.0.4:27017        ESTABLISHED -
tcp        0      0 172.17.0.1:58362        172.17.0.4:27017        ESTABLISHED -
tcp        0      0 172.17.0.1:59148        172.17.0.3:5672         ESTABLISHED -
tcp        0      0 172.17.0.1:59166        172.17.0.3:5672         ESTABLISHED -
tcp        0      0 172.17.0.1:35944        172.17.0.4:27017        ESTABLISHED -
tcp        0      0 172.17.0.1:35912        172.17.0.4:27017        ESTABLISHED -
tcp        0      0 172.17.0.1:35954        172.17.0.4:27017        ESTABLISHED -
tcp        0      0 172.17.0.1:45116        172.17.0.5:6379         ESTABLISHED -
tcp        0      0 172.17.0.1:58354        172.17.0.4:27017        ESTABLISHED -
tcp        0      0 172.17.0.1:35988        172.17.0.4:27017        ESTABLISHED -
tcp        0      0 172.17.0.1:59122        172.17.0.3:5672         ESTABLISHED -
tcp        0      0 192.168.65.2:34936      5.153.231.4:80          TIME_WAIT   -
tcp        0      0 192.168.65.2:44904      151.101.0.204:80        TIME_WAIT   -
tcp        0      0 172.17.0.1:59162        172.17.0.3:5672         ESTABLISHED -
tcp        0      0 172.17.0.1:59180        172.17.0.3:5672         ESTABLISHED -
tcp        0      0 172.17.0.1:45130        172.17.0.5:6379         ESTABLISHED -
tcp        0      0 172.17.0.1:59140        172.17.0.3:5672         ESTABLISHED -
tcp        0      0 172.17.0.1:36002        172.17.0.4:27017        ESTABLISHED -
tcp        0      0 172.17.0.1:35922        172.17.0.4:27017        ESTABLISHED -
tcp        0      0 172.17.0.1:35970        172.17.0.4:27017        ESTABLISHED -
tcp        0      0 172.17.0.1:58364        172.17.0.4:27017        ESTABLISHED -
tcp6       0      0 :::6379                 :::*                    LISTEN      -
tcp6       0      0 :::15672                :::*                    LISTEN      -
tcp6       0      0 :::5672                 :::*                    LISTEN      -
tcp6       0      0 :::27017                :::*                    LISTEN      -

从泊坞窗容器中:

curl -v localhost

正在给予

* Rebuilt URL to: localhost/
* Hostname was NOT found in DNS cache
*   Trying ::1...
* connect to ::1 port 80 failed: Connection refused
*   Trying 127.0.0.1...
* Connected to localhost (127.0.0.1) port 80 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.38.0
> Host: localhost
> Accept: */*
>
< HTTP/1.1 200 OK
* Server nginx/1.10.3 is not blacklisted
< Server: nginx/1.10.3
< Date: Fri,29 Sep 2017 08:46:10 GMT
< Content-Type: text/plain
< Content-Length: 14
< Connection: keep-alive
<
* Connection #0 to host localhost left intact
gangnam style!

但是curl -v website.dev正在返回

* Rebuilt URL to: website.dev/
* Hostname was NOT found in DNS cache
*   Trying 127.0.0.1...
* Connected to website.dev (127.0.0.1) port 80 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.38.0
> Host: website.dev
> Accept: */*
>
< HTTP/1.1 502 Bad Gateway
* Server nginx/1.10.3 is not blacklisted
< Server: nginx/1.10.3
< Date: Fri,29 Sep 2017 08:46:37 GMT
< Content-Type: text/html
< Content-Length: 173
< Connection: keep-alive
<
<html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx/1.10.3</center>
</body>
</html>
* Connection #0 to host website.dev left intact

Docker检查红外线

[
    {
        "Id": "16941d22442a257f0874a772df935514c658ac16ec67eb3f65606b4d7c0ee62e","Created": "2017-09-29T08:31:21.144827953Z","Path": "nginx","Args": [
            "-g","daemon off;"
        ],"State": {
            "Status": "running","Running": true,"Paused": false,"Restarting": false,"OOMKilled": false,"Dead": false,"Pid": 2656,"ExitCode": 0,"Error": "","StartedAt": "2017-09-29T08:31:21.548119911Z","FinishedAt": "0001-01-01T00:00:00Z"
        },"Image": "sha256:25d085baee52923e32f8d134048238fb67e71173e01f758c391119235f7fc565","ResolvConfPath": "/var/lib/docker/containers/16941d22442a257f0874a772df935514c658ac16ec67eb3f65606b4d7c0ee62e/resolv.conf","HostnamePath": "/var/lib/docker/containers/16941d22442a257f0874a772df935514c658ac16ec67eb3f65606b4d7c0ee62e/hostname","HostsPath": "/var/lib/docker/containers/16941d22442a257f0874a772df935514c658ac16ec67eb3f65606b4d7c0ee62e/hosts","LogPath": "/var/lib/docker/containers/16941d22442a257f0874a772df935514c658ac16ec67eb3f65606b4d7c0ee62e/16941d22442a257f0874a772df935514c658ac16ec67eb3f65606b4d7c0ee62e-json.log","Name": "/infra-nginx","RestartCount": 0,"Driver": "aufs","MountLabel": "","ProcessLabel": "","AppArmorProfile": "","ExecIDs": null,"HostConfig": {
            "Binds": null,"ContainerIDFile": "","LogConfig": {
                "Type": "json-file","Config": {}
            },"NetworkMode": "host","PortBindings": {},"RestartPolicy": {
                "Name": "no","MaximumRetryCount": 0
            },"AutoRemove": false,"VolumeDriver": "","VolumesFrom": null,"CapAdd": null,"CapDrop": null,"Dns": [],"DnsOptions": [],"DnsSearch": [],"ExtraHosts": null,"GroupAdd": null,"IpcMode": "","Cgroup": "","Links": null,"OomScoreAdj": 0,"PidMode": "","Privileged": false,"PublishAllPorts": false,"ReadonlyRootfs": false,"SecurityOpt": null,"UTSMode": "","UsernsMode": "","ShmSize": 67108864,"Runtime": "runc","ConsoleSize": [
                0,0
            ],"Isolation": "","CpuShares": 0,"Memory": 0,"NanoCpus": 0,"CgroupParent": "","BlkioWeight": 0,"BlkioWeightDevice": null,"BlkioDeviceReadBps": null,"BlkioDeviceWriteBps": null,"BlkioDeviceReadIOps": null,"BlkioDeviceWriteIOps": null,"CpuPeriod": 0,"CpuQuota": 0,"CpuRealtimePeriod": 0,"CpuRealtimeRuntime": 0,"CpusetCpus": "","CpusetMems": "","Devices": [],"DeviceCgroupRules": null,"DiskQuota": 0,"KernelMemory": 0,"MemoryReservation": 0,"MemorySwap": 0,"MemorySwappiness": -1,"OomKillDisable": false,"PidsLimit": 0,"Ulimits": null,"CpuCount": 0,"CpuPercent": 0,"IOMaximumIOps": 0,"IOMaximumBandwidth": 0
        },"GraphDriver": {
            "Data": null,"Name": "aufs"
        },"Mounts": [],"Config": {
            "Hostname": "moby","Domainname": "","User": "","AttachStdin": false,"AttachStdout": false,"AttachStderr": false,"ExposedPorts": {
                "443/tcp": {},"80/tcp": {}
            },"Tty": false,"OpenStdin": false,"StdinOnce": false,"Env": [
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin","NGINX_VERSION=1.10.3-1~jessie"
            ],"Cmd": [
                "nginx","-g","daemon off;"
            ],"ArgsEscaped": true,"Image": "ajouve/infra-nginx:dev","Volumes": null,"WorkingDir": "","Entrypoint": null,"OnBuild": null,"Labels": {}
        },"NetworkSettings": {
            "Bridge": "","SandboxID": "175272649c9a9c5abbfde7516328bdab5cb3825e1e027eee0580eb18f7ff77cb","HairpinMode": false,"LinkLocalIPv6Address": "","LinkLocalIPv6PrefixLen": 0,"Ports": {},"SandboxKey": "/var/run/docker/netns/default","SecondaryIPAddresses": null,"SecondaryIPv6Addresses": null,"EndpointID": "","Gateway": "","GlobalIPv6Address": "","GlobalIPv6PrefixLen": 0,"IPAddress": "","IPPrefixLen": 0,"IPv6Gateway": "","MacAddress": "","Networks": {
                "host": {
                    "IPAMConfig": null,"Aliases": null,"NetworkID": "3e04a4c12b5a5b3f55e7b4e918dadec64806b5c926fc249e8aa3e28398a02954","EndpointID": "7de54daaa31230c9492a463792015af727e9562eaacbaa0c2d70cdc3d3b04236","DriverOpts": null
                }
            }
        }
    }
]
最佳答案
因此,当您使用–net host运行它时,它实际上仍然不在mac网络上.这就是为什么它不起作用.

documentation开始

The Mac has a changing IP address (or none if you have no network access). From 17.06 onwards our recommendation is to connect to the special Mac-only DNS name docker.for.mac.localhost which will resolve to the internal IP address used by the host.

因此,您需要将配置更改为

worker_processes 4;
pid /run/nginx.pid;

events {}

http {

    server {
      listen 80;
      server_name localhost;
      location / {
          return 200 'gangnam style!';
      }
    }

    server {
      listen 80;
      server_name website.dev;
      location / {
          proxy_pass    http://docker.for.mac.localhost:3000;
          proxy_set_header X-Base-Path "/";
          proxy_set_header Website-Name "test";
      }
    }
}

并且您应该如下运行容器

docker run --name infra-nginx -p 80:80 -d docker-registry.host.com:5000/infra-nginx:dev

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


文章浏览阅读3.7k次,点赞2次,收藏5次。Nginx学习笔记一、Nginx 简介1. 什么是Nginx2. 反向代理3. 负载均衡4. 动静分离二、Nginx基本使用1. Nginx常用的操作命令2. Nginx的配置文件提示:文章写完后,目录可以自动生成,如何生成可参考右边的帮助文档文章目录一、Nginx 简介1. 什么是Nginx2. 反向代理3. 负载均衡4. 动静分离二、Nginx基本使用1. Nginx常用的操作命令2. Nginx的配置文件一、Nginx 简介1. 什么是Nginx  Nginx(“engine x”)是一个_nginx代理
文章浏览阅读1.7w次,点赞14次,收藏61次。我们在使用容器的过程中需,有时候需要对容器中的文件进行修改管理,如果不做文件映射的化,我们使用docker exec -it 容器ID/容器名 /bin/bash 才能进入nginx中的文件里面如图。架设在客户机与目标主机之间,只用于代理内部网络对Internet的连接请求,客户机必须指定代理服务器,并将原本要直接发送到web服务器上的http请求发送到代理服务器中。A想要组C的房子,但是A并不认识C所以租不到,但是B认识C,A找B帮忙租到了C的房子。客户端代理服务器服务器。_docker nginx 配置
文章浏览阅读1.4k次。当用户在访问网站的过程中遇到404错误时,通常情况下应该显示一个友好的错误页面,而不是仅仅显示一个简单的错误提示。在Nginx中,可以通过配置来实现404错误自动跳转到首页的功能。如果您的网站使用动态内容生成页面(如PHP或其他服务器端语言),则应相应地修改配置以适应您的网站架构。这样,当用户访问一个不存在的页面时,Nginx会自动将其重定向到首页。为了使配置生效,需要重新加载Nginx配置。首先,需要打开Nginx的配置文件。现在,当用户访问一个不存在的页面时,Nginx会自动将其重定向到首页。_nginx 404 重定向
文章浏览阅读2.7k次。docker 和 docker-compose 部署 nginx+mysql+wordpress 实战_docker wordpress mariadb
文章浏览阅读1.3k次。5:再次启动nginx,可以正常启动,可以在任务管理器中查看到nginx的进程。重新启动下 直接访问8090端口 ok 访问成功。1 :查看80端口占用情况,pid的值为3960。3:在运行中输入regedit打开注册表编辑器。2: 通过以下命令查看3960所对应的服务名称。4:找到Start,右键修改将其制改为4。_nginx80端口无法访问
文章浏览阅读3.1w次,点赞105次,收藏182次。高性能:Nginx 被设计为能够处理大量并发连接而不显著增加系统负担。它采用异步事件驱动的架构,可以有效地处理高流量的 Web 请求。负载均衡:Nginx 支持负载均衡,可以将请求分发到多个后端服务器,以提高网站性能和可用性。反向代理:Nginx 可以充当反向代理,将客户端请求转发到后端服务器,隐藏后端服务器的真实 IP 地址,增加安全性和可扩展性。静态文件服务:Nginx 可以高效地提供静态文件(如 HTML、CSS、JavaScript、图像等)的服务,减轻应用服务器的负担。
文章浏览阅读976次。nginx作为常用的web代理服务器,某些场景下对于性能要求还是蛮高的,所以本片文章会基于操作系统调度以及网络通信两个角度来讨论一下Nginx性能的优化思路。我们的大学教程大部分讲述七层模型,实际上现代网络协议使用的都是四层模型,如下图,应用层报文经过四层的首部封装到对端。对端链路层拆开首部查看mac地址是自己在网上,拆开ip首部查看目的地址是不是自己,然后到达传输层应用层完成报文接收。文章是基于原有个人知识基础上,对旧知识进行巩固,以及新知识实践学习。
文章浏览阅读5.4k次,点赞9次,收藏15次。最后再说一种情况,就是后端处理了跨域,就不需要自己在处理了(这里吐槽下,某些后端工程师自己改服务端代码解决跨域,但是又不理解其中原理,网上随便找段代码黏贴,导致响应信息可能处理不完全,如method没添加全,headers没加到点上,自己用的那个可能复制过来的并不包含实际项目所用到的,没有添加options请求返回状态码等,导致Nginx再用通用的配置就会可能报以下异常)里面的就好了,因为这里如果是预检请求直接就ruturn了,请求不会再转发到59200服务,如果也删除了,就会报和情况1一样的错误。_nginx 允许跨域
文章浏览阅读2.5k次。项目配置了多个域名,如下,php 代码中有获取的值。当访问a.demo.com时,其获取的值是符合预期的。但是当访问b.demo.com时,其获取的值还是a.demo.com,导致代码中的判断出现错误。_nginxservername多个域名
文章浏览阅读1k次,点赞2次,收藏5次。采用YAML manifest的方式来安装ingress-nginx,用registry.lank8s.cn镜像库来替换 registry.k8s.io的库。_ingress-nginx安装
文章浏览阅读1.6k次,点赞2次,收藏2次。在windows平台编译nginx_windows 编译nginx
文章浏览阅读5.8k次,点赞2次,收藏18次。nginx [engine x] 是 HTTP 和反向代理服务器、邮件代理服务器和通用 TCP/UDP 代理服务器。nginx 的特点是占有内存少,并发能力强,事实上 nginx 的并发能力确实在同类型的网页服务器中表现较好,中国大陆使用nginx网站用户有:百度、京东、新浪、网易、腾讯、淘宝等。在高连接并发的情况下,nginx是Apache服务器不错的替代品,能够支持高达50000个并发连接数的响应。使用epoll and kqueue作为开发模型。_nginx
文章浏览阅读2k次。Linux启动(systemctl start nginx)nginx服务时出现:Failed to start nginx.service: Unit not found._为什么nginx的systemctl start nginx.service不能使用
文章浏览阅读1.3k次。重启之后,打开浏览器,输入http://localhost:8900/myBaidu,这时候就会自动的跳转到百度的页面。按照我们不同的需求修改nginx文件夹中的nginx-1.16.1conf里面的nginx.conf文件。启动nginx:打开nginx的文件夹,然后双击nginx.exe文件,启动nginx。打开之后假设我们需要跳转到百度则在配置文件nginx.conf中的下面加上。1、打开任务管理器关闭nginx的进程。端口在配置文件的(下图)进行查看nginx端口。_nginx 代理百度
文章浏览阅读5.7k次,点赞5次,收藏3次。nginx重定向问题解决(rewrite or internal redirection cycle)_rewrite or internal redirection cycle while internally redirecting to "/inde
文章浏览阅读1.3k次。请注意,上述命令假设 Nginx 已经在系统的 PATH 环境变量中配置。如果没有,请提供正确的 Nginx 安装路径,或者在命令中使用完整的路径来替换。将该命令与所有 Nginx 进程的 PID 一起使用,以终止所有正在运行的 Nginx 进程。此命令将启动一个新的 Nginx 进程来重新加载配置文件并重新启动服务器。使用以下命令来终止所有 Nginx 进程(使用上面的 PID 替换。的进程以及它们的 PID。打开命令提示符(CMD)。此命令将列出所有名为。选项来强制终止进程。_windows 怎么关闭nginx
文章浏览阅读2.7k次,点赞2次,收藏7次。包括 Netflix、GitHub 和 WordPress。Nginx 可以用作 Web 服务器、负载均衡器、反向代理和 HTTP 缓存等。_ubuntu安装nginx
文章浏览阅读915次。轻松搭建短域名短链接服务系统,可选权限认证,并自动生成证书认证把nginx的http访问转换为https加密访问,完整步骤和代码。_nginx 短链代理
文章浏览阅读1.1k次,点赞35次,收藏24次。流媒体方案之Nginx——实现物联网视频监控项目Nginx是什么Nginx在流媒体方案中的位置软硬件准备移植编译Nginx运行Ngnix测试流媒体方案浏览器播放_nginx-rtmp-module
文章浏览阅读1.9k次。nginx 配置 wss 协议转发 ws 服务器_nginx 配置wss