0
我使用的是docker和docker-compose的dinghy。我有一个docker image for fake_sqs,这我加载在我的码头工人,组成像这样:使用Docker&Dinghy抑制请求输出
fakesqs:
image: link664/fakesqs-docker
command: bundle exec fake_sqs -n fakesqs -p 4568
environment:
VIRTUAL_HOST: aws.docker
我也有运行并连接到图像轮询脚本:
poller:
build: poller/.
command: script/poller
volumes:
- ./poller:/app
links:
- fakesqs
environment:
AWS_QUEUE_NAME: my-queue
AWS_ENDPOINT: http://fakesqs:4568/
这一切愉快地工作。轮询者可以从fake_sqs中读取,这很好。我遇到的问题是,每次轮询命中队列(即每秒几次),它记录请求到stdout:
fakesqs_1 | [2016-07-27 07:59:29] INFO WEBrick 1.3.1
fakesqs_1 | [2016-07-27 07:59:29] INFO ruby 2.2.3 (2015-08-18) [x86_64-linux]
fakesqs_1 | == Sinatra (v1.4.7) has taken the stage on 4568 for development with backup from WEBrick
fakesqs_1 | [2016-07-27 07:59:29] INFO WEBrick::HTTPServer#start: pid=1 port=4568
poller_1 | Creating queue my-queue
fakesqs_1 | 172.17.0.11 - - [27/Jul/2016:08:00:00 UTC] "POST/HTTP/1.1" 200 273
fakesqs_1 | - ->/
poller_1 | Initializing poller for queue http://fakesqs:4568/my-queue
poller_1 | Polling ...
fakesqs_1 | 172.17.0.11 - - [27/Jul/2016:08:00:00 UTC] "POST /my-queue HTTP/1.1" 200 221
fakesqs_1 | - -> /my-queue
fakesqs_1 | 172.17.0.11 - - [27/Jul/2016:08:00:01 UTC] "POST /my-queue HTTP/1.1" 200 221
fakesqs_1 | - -> /my-queue
fakesqs_1 | 172.17.0.11 - - [27/Jul/2016:08:00:01 UTC] "POST /my-queue HTTP/1.1" 200 221
fakesqs_1 | - -> /my-queue
fakesqs_1 | 172.17.0.11 - - [27/Jul/2016:08:00:01 UTC] "POST /my-queue HTTP/1.1" 200 221
fakesqs_1 | - -> /my-queue
fakesqs_1 | 172.17.0.11 - - [27/Jul/2016:08:00:01 UTC] "POST /my-queue HTTP/1.1" 200 221
fakesqs_1 | - -> /my-queue
如何抑制这种请求日志记录不完全抑制STDOUT?
如何调整Dockerfile中的日志记录级别? – link664
这将是特定于应用程序。 fakesqs可能需要一个配置设置来调整日志记录。 – dnephin