WordPress Docker组成的磁盘空间正在爆炸
我有一个带有Docker-Compose的WordPress项目。我正在托管Digitalocean上的项目,并在空间上遇到问题。客户认识到他几天/几周后无法上传新图像。我执行了Docker System Prune -all
,并能够清除一些空间并上传新媒体。但是片刻之后,磁盘空间再次满。 /var/lib/docker/oferlay2
就像25GB。这是什么如何解决此问题?
更新1:Docker System Prune - All
现在给我总回收空间:0B
更新2:我能够上传一些媒体并在执行以下后再次更改页面内容命令。问题仍然在于,此修复仅持续几个小时,几个小时后,没有什么可以改变了。
docker kill $(docker ps -q)
docker system prune
sudo service apache2 stop
docker-compose up -d
更新3:我进行了一些研究,并在/var/lib/docker/containers/id/hash-json.log
中找到了17GB logFile,
我如何限制此文件大小?
服务器上的空间:
这就是我的docker-compose.yml
看起来像:
services:
db:
image: mysql:5.7
volumes:
- db_data:/var/lib/mysql
restart: always
environment:
MYSQL_ROOT_PASSWORD: xx
MYSQL_DATABASE: xx
MYSQL_USER: xx
MYSQL_PASSWORD: xx
wordpress:
depends_on:
- db
image: wordpress:latest
volumes:
- wordpress_data:/var/www/html
- ./uploads.ini:/usr/local/etc/php/conf.d/uploads.ini
- ./my_theme:/var/www/html/wp-content/themes/my_theme
ports:
- "80:80"
restart: always
environment:
WORDPRESS_DB_HOST: db:3306
WORDPRESS_DB_USER: xx
WORDPRESS_DB_PASSWORD: xx
WORDPRESS_DB_NAME: xx
phpmyadmin:
image: corbinu/docker-phpmyadmin
links:
- db:mysql
ports:
- 8181:80
environment:
MYSQL_USERNAME: xx
MYSQL_ROOT_PASSWORD: xx
MYSQL_PORT_3306_TCP_ADDR: db
volumes:
db_data: {}
wordpress_data: {}```
I have an Wordpress Project running with docker-compose. I am hosting the project on Digitalocean and have an issue with the space. The client recognised he couldn't upload new images after days/weeks. I executed docker system prune --all
and was able to clear some space and upload new media. But after a little time the disk space is full again. /var/lib/docker/overlay2
is like 25GB. What is this & how can i fix this issue?
Update 1: docker system prune --all
now gives me Total reclaimed space: 0B
Update 2: I was able to upload some media and change page content again after executing the following commands. The Problem is still that this fix only lasts for some hours and after hours nothing is changeable anymore.
docker kill $(docker ps -q)
docker system prune
sudo service apache2 stop
docker-compose up -d
Update 3: I investigated a little bit and found a 17GB logfile inside /var/lib/docker/containers/ID/HASH-json.log
How can i limit this file size?
Space on server:
This is how my docker-compose.yml
looks like:
services:
db:
image: mysql:5.7
volumes:
- db_data:/var/lib/mysql
restart: always
environment:
MYSQL_ROOT_PASSWORD: xx
MYSQL_DATABASE: xx
MYSQL_USER: xx
MYSQL_PASSWORD: xx
wordpress:
depends_on:
- db
image: wordpress:latest
volumes:
- wordpress_data:/var/www/html
- ./uploads.ini:/usr/local/etc/php/conf.d/uploads.ini
- ./my_theme:/var/www/html/wp-content/themes/my_theme
ports:
- "80:80"
restart: always
environment:
WORDPRESS_DB_HOST: db:3306
WORDPRESS_DB_USER: xx
WORDPRESS_DB_PASSWORD: xx
WORDPRESS_DB_NAME: xx
phpmyadmin:
image: corbinu/docker-phpmyadmin
links:
- db:mysql
ports:
- 8181:80
environment:
MYSQL_USERNAME: xx
MYSQL_ROOT_PASSWORD: xx
MYSQL_PORT_3306_TCP_ADDR: db
volumes:
db_data: {}
wordpress_data: {}```
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
/dev/vda1
也托管Docker容器也已满,因此您的叠加层无法长大。我建议您进行:
The
/dev/vda1
, which hosts docker containers too, is full, so your overlays cannot grow up.I suggest you to:
我通过为记录文件设置最大尺寸限制来解决此问题。
I fixed this issue by setting a max size limit for logging files.