apache-Docker消息:由于来自服务器/代理的错误响应,自动禁用Acquire :: http :: Pipeline-Depth

前端之家收集整理的这篇文章主要介绍了apache-Docker消息:由于来自服务器/代理的错误响应,自动禁用Acquire :: http :: Pipeline-Depth 前端之家小编觉得挺不错的,现在分享给大家,也给大家做个参考。

将apache2安装到Docker的Ubuntu 16.04映像中,我得到以下消息

W: http://archive.ubuntu.com/ubuntu/pool/main/g/gdbm/libgdbm3_1.8.3-13.1_amd64.deb: Automatically disabled Acquire::http::Pipeline-Depth due to incorrect response from server/proxy. (man 5 apt.conf).

那就是Dockerfile:

FROM ubuntu:16.04

#RUN apt-get update
#https://github.com/phusion/baseimage-docker/issues/319
RUN apt-get update && apt-get install -y --no-install-recommends apt-utils 
RUN apt-get install -y apache2

当我打开图像时,我看到了/ var / www / html文件夹,即安装了apache.

那是什么信息?是错误还是我可以认为apache已完全安装?

最佳答案
流水线是HTTP / 1.1协议的功能.从RFC 7230开始:

A client that supports persistent connections MAY “pipeline” its@H_404_30@ requests (i.e.,send multiple requests without waiting for each@H_404_30@ response). A server MAY process a sequence of pipelined requests in@H_404_30@ parallel if they all have safe methods (Section 4.2.1 of [RFC7231]),@H_404_30@ but it MUST send the corresponding responses in the same order that@H_404_30@ the requests were received.

可以通过设置Acquire :: http :: Pipeline-Depth激活此功能.从man apt.conf开始:

The setting Acquire::http::Pipeline-Depth can be used to enable HTTP pipelining (RFC 2616 section 8.1.2.2) which can be beneficial e.g. on high-latency connections. It specifies how many requests are sent in a pipeline. APT tries to detect and workaround misbehaving webservers and proxies at runtime,but if you know that yours does not conform to the HTTP/1.1 specification pipelining can be disabled by setting the value to 0. It is enabled by default with the value 10.

您看到的消息表示您与apt信息库的连接不支持管道传输(可能是由于某种代理),并且apt自动禁用了此功能.安装可能会花费更多时间,但是您可以认为apache服务器已完全安装.

原文链接:https://www.f2er.com/docker/532756.html

猜你在找的Docker相关文章