Docker 容器未启动,因为 rabbit 磁盘空间不足 [英] Docker container not started because rabbit is out of disc space
本文介绍了Docker 容器未启动,因为 rabbit 磁盘空间不足的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!
问题描述
RabbitMQ 似乎占用了太多磁盘空间并且无法启动.如何在我的 Mac 上删除它?我似乎找不到它.我已经尝试删除所有图像和容器,然后从头开始重建,希望它能解决问题.
RabbitMQ seems to have taken too much diskspace and doesn't start. How can I delete it on my Mac? I cannot seem to find it. I already tried deleting all images and containers and then rebuild from scratch hoping it would solve the problem.
$docker logs rabbitmq
RabbitMQ 3.6.6. Copyright (C) 2007-2016 Pivotal Software, Inc.
## ## Licensed under the MPL. See http://www.rabbitmq.com/
## ##
########## Logs: tty
###### ## tty
##########
Starting broker...
=INFO REPORT==== 11-Dec-2016::10:06:13 ===
Starting RabbitMQ 3.6.6 on Erlang 19.0.7
Copyright (C) 2007-2016 Pivotal Software, Inc.
Licensed under the MPL. See http://www.rabbitmq.com/
=INFO REPORT==== 11-Dec-2016::10:06:13 ===
node : rabbit@538f7beedbe3
home dir : /var/lib/rabbitmq
config file(s) : /etc/rabbitmq/rabbitmq.config
cookie hash : kOyaDgypIBcP8tZ01/3Fdg==
log : tty
sasl log : tty
database dir : /var/lib/rabbitmq/mnesia/rabbit@538f7beedbe3
=INFO REPORT==== 11-Dec-2016::10:06:18 ===
Memory limit set to 799MB of 1997MB total.
=INFO REPORT==== 11-Dec-2016::10:06:18 ===
Disk free limit set to 50MB
=INFO REPORT==== 11-Dec-2016::10:06:18 ===
Disk free space insufficient. Free bytes:0 Limit:50000000
=WARNING REPORT==== 11-Dec-2016::10:06:18 ===
disk resource limit alarm set on node rabbit@538f7beedbe3.
**********************************************************
*** Publishers will be blocked until this alarm clears ***
**********************************************************
=INFO REPORT==== 11-Dec-2016::10:06:18 ===
Limiting to approx 1048476 file handles (943626 sockets)
=INFO REPORT==== 11-Dec-2016::10:06:18 ===
FHC read buffering: OFF
FHC write buffering: ON
=INFO REPORT==== 11-Dec-2016::10:06:18 ===
Database directory at /var/lib/rabbitmq/mnesia/rabbit@538f7beedbe3 is empty. Initialising from scratch...
=INFO REPORT==== 11-Dec-2016::10:06:18 ===
application: mnesia
exited: stopped
type: temporary
=CRASH REPORT==== 11-Dec-2016::10:06:18 ===
crasher:
initial call: application_master:init/4
pid: <0.116.0>
registered_name: []
exception exit: {{cannot_create_schema,
{file_error,
"/var/lib/rabbitmq/mnesia/rabbit@538f7beedbe3/rabbit@538f7beedbe3514846847780.BUPTMP",
enospc}},
{rabbit,start,[normal,[]]}}
in function application_master:init/4 (application_master.erl, line 134)
ancestors: [<0.115.0>]
messages: [{'EXIT',<0.117.0>,normal}]
links: [<0.115.0>,<0.31.0>]
dictionary: []
trap_exit: true
status: running
heap_size: 1598
stack_size: 27
reductions: 98
neighbours:
=INFO REPORT==== 11-Dec-2016::10:06:18 ===
application: rabbit
exited: {{cannot_create_schema,
{file_error,
"/var/lib/rabbitmq/mnesia/rabbit@538f7beedbe3/rabbit@538f7beedbe3514846847780.BUPTMP",
enospc}},
{rabbit,start,[normal,[]]}}
type: temporary
=INFO REPORT==== 11-Dec-2016::10:06:18 ===
application: ranch
exited: stopped
type: temporary
=INFO REPORT==== 11-Dec-2016::10:06:18 ===
application: os_mon
exited: stopped
type: temporary
BOOT FAILED
===========
Error description:
{could_not_start,rabbit,
{{cannot_create_schema,
{file_error,
"/var/lib/rabbitmq/mnesia/rabbit@538f7beedbe3/rabbit@538f7beedbe3514846847780.BUPTMP",
enospc}},
{rabbit,start,[normal,[]]}}}
Log files (may contain more information):
tty
tty
=INFO REPORT==== 11-Dec-2016::10:06:18 ===
application: amqp_client
exited: stopped
type: temporary
=INFO REPORT==== 11-Dec-2016::10:06:18 ===
application: syntax_tools
exited: stopped
type: temporary
=INFO REPORT==== 11-Dec-2016::10:06:18 ===
application: rabbit_common
exited: stopped
type: temporary
=INFO REPORT==== 11-Dec-2016::10:06:18 ===
application: xmerl
exited: stopped
type: temporary
=INFO REPORT==== 11-Dec-2016::10:06:18 ===
application: asn1
exited: stopped
type: temporary
=INFO REPORT==== 11-Dec-2016::10:06:18 ===
application: inets
exited: stopped
type: temporary
=INFO REPORT==== 11-Dec-2016::10:06:18 ===
Error description:
{could_not_start,rabbit,
{{cannot_create_schema,
{file_error,
"/var/lib/rabbitmq/mnesia/rabbit@538f7beedbe3/rabbit@538f7beedbe3514846847780.BUPTMP",
enospc}},
{rabbit,start,[normal,[]]}}}
Log files (may contain more information):
tty
tty
{"init terminating in do_boot",{could_not_start,rabbit,{{cannot_create_schema,{file_error,"/var/lib/rabbitmq/mnesia/rabbit@538f7beedbe3/rabbit@538f7beedbe3514846847780.BUPTMP",enospc}},{rabbit,start,[normal,[]]}}}}
init terminating in do_boot ()
Crash dump is being written to: erl_crash.dump...
我可以在我的 docker-compose.yml 中为 Rabbit 定义一个物理卷吗?
Could I definde a physical volume for Rabbit in my docker-compose.yml?
推荐答案
这两个命令完成了工作:
These two commands did the job:
docker rmi $(docker images -q) //removes all images
docker volume rm $(docker volume ls -f dangling=true -q) // removes all volumes
这篇关于Docker 容器未启动,因为 rabbit 磁盘空间不足的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!
查看全文