docker - 在 Docker 上设置 Varnish + Drupal
问题描述
我有三个 docker 容器,一个运行 php5+apache 并安装了 Drupal,另一个运行 varnish 4.1,最后一个运行 MySQL。这是我的 docker-compose.yml
version: "2"
services:
app:
container_name: drupal.app
build: .build/php5-apache
working_dir: "/var/www/html/"
ports:
- "8080:80"
volumes:
- ".:/var/www/html/"
restart: always
networks:
vpcbr:
ipv4_address: 10.5.0.5
links:
- db
db:
container_name: drupal.db
#image: mysql:5.5
build: .build/mysql
ports:
- "3306:3306"
environment:
MYSQL_ROOT_PASSWORD: dskjfskjhfnksdnf
volumes:
- ./data/mysql:/var/lib/mysql
networks:
vpcbr:
ipv4_address: 10.5.0.4
restart: always
varnish:
container_name: drupal.varnish
build: .build/varnish
ports:
- "80:80"
networks:
vpcbr:
ipv4_address: 10.5.0.3
restart: always
tty: true
networks:
vpcbr:
driver: bridge
ipam:
config:
- subnet: 10.5.0.0/16
gateway: 10.5.0.1
这是清漆的 default.vcl
#
# This is an example VCL file for Varnish.
#
# It does not do anything by default, delegating control to the
# builtin VCL. The builtin VCL is called when there is no explicit
# return statement.
#
# See the VCL chapters in the Users Guide at https://www.varnish-cache.org/docs/
# and https://www.varnish-cache.org/trac/wiki/VCLExamples for more examples.
# Marker to tell the VCL compiler that this VCL has been adapted to the
# new 4.0 format.
vcl 4.0;
# Default backend definition. Set this to point to your content server.
backend default {
.host = "10.5.0.5";
.port = "80";
}
sub vcl_recv {
# Happens before we check if we have this in cache already.
#
# Typically you clean up the request here, removing cookies you don't need,
# rewriting the request, etc.
set req.backend_hint = bar.backend();
# Do not cache these paths.
if (req.url ~ "^/status\.php$" ||
req.url ~ "^/update\.php" ||
req.url ~ "^/install\.php" ||
req.url ~ "^/apc\.php$" ||
req.url ~ "^/admin" ||
req.url ~ "^/admin/.*$" ||
req.url ~ "^/user" ||
req.url ~ "^/user/.*$" ||
req.url ~ "^/users/.*$" ||
req.url ~ "^/info/.*$" ||
req.url ~ "^/flag/.*$" ||
req.url ~ "^.*/ajax/.*$" ||
req.url ~ "^.*/ahah/.*$" ||
req.url ~ "^/system/files/.*$") {
return (pass);
}
# Always cache the following file types for all users. This list of extensions
# appears twice, once here and again in vcl_backend_response so make sure you edit both
# and keep them equal.
if (req.url ~ "(?i)\.(pdf|asc|dat|txt|doc|xls|ppt|tgz|csv|png|gif|jpeg|jpg|ico|swf|css|js)(\?.*)?$") {
unset req.http.Cookie;
}
# Remove all cookies that Drupal doesn't need to know about. We explicitly
# list the ones that Drupal does need, the SESS and NO_CACHE. If, after
# running this code we find that either of these two cookies remains, we
# will pass as the page cannot be cached.
if (req.http.Cookie) {
# 1. Append a semi-colon to the front of the cookie string.
# 2. Remove all spaces that appear after semi-colons.
# 3. Match the cookies we want to keep, adding the space we removed
# previously back. (\1) is first matching group in the regsuball.
# 4. Remove all other cookies, identifying them by the fact that they have
# no space after the preceding semi-colon.
# 5. Remove all spaces and semi-colons from the beginning and end of the
# cookie string.
set req.http.Cookie = ";" + req.http.Cookie;
set req.http.Cookie = regsuball(req.http.Cookie, "; +", ";");
set req.http.Cookie = regsuball(req.http.Cookie, ";(SESS[a-z0-9]+|SSESS[a-z0-9]+|NO_CACHE)=", "; \1=");
set req.http.Cookie = regsuball(req.http.Cookie, ";[^ ][^;]*", "");
set req.http.Cookie = regsuball(req.http.Cookie, "^[; ]+|[; ]+$", "");
if (req.http.Cookie == "") {
# If there are no remaining cookies, remove the cookie header. If there
# aren't any cookie headers, Varnish's default behavior will be to cache
# the page.
unset req.http.Cookie;
}
else {
# If there is any cookies left (a session or NO_CACHE cookie), do not
# cache the page. Pass it on to Apache directly.
return (pass);
}
}
}
sub vcl_backend_response {
# Happens after we have read the response headers from the backend.
#
# Here you clean the response headers, removing silly Set-Cookie headers
# and other mistakes your backend does.
}
sub vcl_deliver {
# Happens when we have all the pieces we need, and are about to send the
# response to the client.
#
# You can do accounting or modifying the final object here.
}
我用curl测试了varnish服务器是否可以通过ip 10.5.0.5连接到drupal服务器,结果是肯定的。
但是,每当我尝试通过http://localhost/访问网络时访问网络时,varnish 总是给我 503 错误并且无法获取后端。
谁能告诉我我的 default.vcl 设置或 docker-compose 设置有什么问题。
解决方案
您尝试http://localhost
从哪里访问 URL?
据我所知,清漆缓存应该放在另一个实例中,而不是您尝试缓存内容的同一个实例中。因此,您应该将 URL 指向不应该是10.5.0.5
.
您的 Vanish VCL 设置似乎是正确的,它正在监听从10.5.0.5
端口缓存内容80
。
推荐阅读
- angular - 无法检查是否启用或禁用按钮
- r - R - 在每个数据框中用文件名重命名特定列
- javascript - 将元素与数据属性值的一部分匹配?
- java - 获取 java.lang.OutOfMemoryError: Java heap space while running twitter connector using flume
- git - 重新标记泊坞窗图像
- java - 转换 JavaRDD
到 JavaPairRDD
- python-3.x - cumsum 与平均值 - python
- scala - 执行目标 org.apache.maven.plugins:maven-assembly-plugin:2.5:single failed.: NullPointerException
- codeigniter - 我的网址被重定向到其他链接
- python - 如何在 sqlalchemy 中进行数据库模式迁移?