blocks|key|4372422|text|在Docker+for+Windows和Mac上，可能还有其他操作系统，可以使用tail选项。例如：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4372423|docker+logs+-f+--tail+100|code-block|syntax|javascript|4372424|这样，只会显示最后100行，而不必先滚动1M行……|4372425|(因此，删除日志可能是不必要的)|4372426|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

On Docker for Windows and Mac, and probably others too, it is possible to use the tail option. For example:
<pre class="lang-sh prettyprint-override"><code>docker logs -f --tail 100
</code></pre>
This way, only the last 100 lines are shown, and you don't have first to scroll through 1M lines...
(And thus, deleting the log is probably unnecessary)

blocks|key|4372336|text|sudo+sh+-c+"truncate+-s+0+/var/lib/docker/containers/*/*-json.log"|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|4372337|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>sudo sh -c "truncate -s 0 /var/lib/docker/containers/*/*-json.log"
</code></pre>

blocks|key|4371762|text|您可以设置logrotate定期清除日志。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4371763|/etc/logrotate.d/docker-logs中的示例文件|4371764|/var/lib/docker/containers/*/*.log+{
+rotate+7
+daily
+compress
+size=50M
+missingok
+delaycompress
+copytruncate
}|code-block|syntax|javascript|4371765|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

You can set up logrotate to clear the logs periodically.

Example file in /etc/logrotate.d/docker-logs

<pre><code>/var/lib/docker/containers/*/*.log {
 rotate 7
 daily
 compress
 size=50M
 missingok
 delaycompress
 copytruncate
}
</code></pre>

blocks|key|4371841|text|Docker4Mac，2018年解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4371842|LOGPATH=$(docker+inspect+--format='{{.LogPath}}'+<container_name_or_id>)
docker+run+-it+--rm+--privileged+--pid=host+alpine:latest+nsenter+-t+1+-m+-u+-n+-i+--+truncate+-s0+$LOGPATH|code-block|syntax|javascript|4371843|第一行获取日志文件路径，类似于接受的答案。|4371844|第二行使用nsenter，它允许您在作为Docker4Mac下所有停靠容器主机的xhyve+VM中运行命令。我们运行的命令是来自非Mac答案的熟悉的truncate+-s0+$LOGPATH。|offset|length|style|CODE|4371845|如果你使用的是docker-compose，第一行变成：|4371846|local+LOGPATH=$(docker+inspect+--format='{{.LogPath}}'+$(docker-compose+ps+-q+<service>))|4371847|<service>是docker-compose.yml文件中的服务名称。|4371848|感谢https://github.com/justincormack/nsenter1的nsenter技巧。|4371849|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/justincormack/nsenter1^0|0|0|0|5|7|14|5|22|L|0|7|E|0|0|0|9|A|I|0|18|7|2|15|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|16|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|17|8|@$K|18|L|19|M|N]|$K|1A|L|1B|M|N]|$K|1C|L|1D|M|N]]|9|@]|A|$]]|$1|O|3|P|5|6|7|1E|8|@$K|1F|L|1G|M|N]]|9|@]|A|$]]|$1|Q|3|R|5|D|7|1H|8|@]|9|@]|A|$E|F]]|$1|S|3|T|5|6|7|1I|8|@$K|1J|L|1K|M|N]|$K|1L|L|1M|M|N]]|9|@]|A|$]]|$1|U|3|V|5|6|7|1N|8|@$K|1O|L|1P|M|N]]|9|@$K|1Q|L|1R|1|1S]]|A|$]]|$1|W|3|-4|5|6|7|1T|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|13]]]]

Docker4Mac, a 2018 solution:

<pre><code>LOGPATH=$(docker inspect --format='{{.LogPath}}' &lt;container_name_or_id&gt;)
docker run -it --rm --privileged --pid=host alpine:latest nsenter -t 1 -m -u -n -i -- truncate -s0 $LOGPATH
</code></pre>

The first line gets the log file path, similar to the accepted answer.

The second line uses <code>nsenter</code> that allows you to run commands in the <code>xhyve</code> VM that servers as the host for all the docker containers under Docker4Mac. The command we run is the familiar <code>truncate -s0 $LOGPATH</code> from non-Mac answers.

If you're using <code>docker-compose</code>, the first line becomes:

<pre><code>local LOGPATH=$(docker inspect --format='{{.LogPath}}' $(docker-compose ps -q &lt;service&gt;))
</code></pre>

and <code>&lt;service&gt;</code> is the service name from your <code>docker-compose.yml</code> file.

Thanks to <a href="https://github.com/justincormack/nsenter1" rel="noreferrer">https://github.com/justincormack/nsenter1</a> for the <code>nsenter</code> trick.

blocks|key|4372065|text|以下是清理docker容器日志的跨平台解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4372066|docker+run+--rm+-v+/var/lib/docker:/var/lib/docker+alpine+sh+-c+"echo+''+>+$(docker+inspect+--format='{{.LogPath}}'+CONTAINER_NAME)"|code-block|syntax|javascript|4372067|将其粘贴到您的终端中，并将CONTAINER_NAME更改为所需的容器名称或id。|offset|length|style|CODE|4372068|entityMap^0|0|0|D|E|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Here is a cross platform solution to clearing docker container logs:
<pre><code>docker run --rm -v /var/lib/docker:/var/lib/docker alpine sh -c &quot;echo '' &gt; $(docker inspect --format='{{.LogPath}}' CONTAINER_NAME)&quot;
</code></pre>
Paste this into your terminal and change <code>CONTAINER_NAME</code> to desired container name or id.

blocks|key|4371936|text|在我的Ubuntu服务器上，即使是sudo，我也会得到Cannot+open+‘/var/lib/docker/containers/*/*-json.log’+for+writing:+No+such+file+or+directory|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4371937|但是梳理docker+inspect和truncate回答起作用了：|4371938|sudo+truncate+-s+0+`docker+inspect+--format='{{.LogPath}}'+<container>`|code-block|syntax|javascript|4371939|entityMap^0|R|2K|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|R|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|S|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

On my Ubuntu servers even as sudo I would get <code>Cannot open ‘/var/lib/docker/containers/*/*-json.log’ for writing: No such file or directory</code>

But combing the docker inspect and truncate answers worked :

<pre><code>sudo truncate -s 0 `docker inspect --format='{{.LogPath}}' &lt;container&gt;`
</code></pre>

blocks|key|4372579|text|我不确定这是否对你有帮助，但移除容器总是有帮助的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4372580|因此，如果您使用docker-compose进行设置，则可以简单地使用docker-compose+down+&&+docker-compose+up而不是docker-compose+restart。有了适当的设置(确保对持久数据使用卷挂载)，这样就不会丢失任何数据。|offset|length|style|CODE|4372581|当然，这比操作员要求的要多。但在各种情况下，其他答案无法提供帮助(如果使用远程docker服务器或在Windows计算机上工作，则访问底层文件系统是专有的且困难的)|4372582|entityMap^0|0|Z|14|26|M|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]|$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|K|$]]

Not sure if this is helpful for you, but removing the container always helps.
So, if you use docker-compose for your setup, you can simply use <code>docker-compose down &amp;&amp; docker-compose up</code> instead of <code>docker-compose restart</code>. With a proper setup (make sure to use volume mounts for persistent data), you don't lose any data this way.
Sure, this is more than the OP requested. But there are various situations where the other answers cannot help (if using a remote docker server or working on a Windows machine, accessing the underlying filesystem is proprietary and difficult)

blocks|key|4372525|text|我确实更喜欢这个(来自上面的解决方案)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4372526|truncate+-s+0+/var/lib/docker/containers/*/*-json.log|code-block|syntax|javascript|4372527|然而，我正在运行几个系统(例如Ubuntu+18.x+Bionic+)，在这些系统中，这个路径并不像预期的那样工作。Docker是通过Snap安装的，所以容器的路径更像是：|4372528|truncate+-s+0+/var/snap/docker/common/var-lib-docker/containers/*/*-json.log|4372529|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I do prefer this one (from solutions above):

<pre><code>truncate -s 0 /var/lib/docker/containers/*/*-json.log
</code></pre>

However I'm running several systems (Ubuntu 18.x Bionic for example), where this path does not work as expected. Docker is installed through Snap, so the path to containers is more like:

<pre><code>truncate -s 0 /var/snap/docker/common/var-lib-docker/containers/*/*-json.log
</code></pre>

blocks|key|4372690|text|多亏了answer+by+@BMitch，我刚刚编写了一个shell脚本来清理所有容器的日志：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4372691|#!/bin/bash
ids=$(docker+ps+-a+--format='{{.ID}}')
for+id+in+$ids
do
++++++++echo+$(docker+ps+-a+--format='{{.ID}}+###+{{.Names}}+###+{{.Image}}'+%7C+fgrep+$id)
++++++++truncate+-s+0+$(docker+inspect+--format='{{.LogPath}}'+$id)
++++++++ls+-llh+$(docker+inspect+--format='{{.LogPath}}'+$id)
done|code-block|syntax|javascript|4372692|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/42510314/659077^0|3|H|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

Thanks to <a href="https://stackoverflow.com/a/42510314/659077">answer by @BMitch</a>, I've just wrote a shell script to clean logs of all the containers:
<pre><code>#!/bin/bash
ids=$(docker ps -a --format='{{.ID}}')
for id in $ids
do
 echo $(docker ps -a --format='{{.ID}} ### {{.Names}} ### {{.Image}}' | fgrep $id)
 truncate -s 0 $(docker inspect --format='{{.LogPath}}' $id)
 ls -llh $(docker inspect --format='{{.LogPath}}' $id)
done
</code></pre>

blocks|key|4372644|text|sudo+find+/var/lib/docker/containers/+-type+f+-name+"*.log"+-delete|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|4372645|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>sudo find /var/lib/docker/containers/ -type f -name &quot;*.log&quot; -delete
</code></pre>

I use <code>docker logs [container-name]</code> to see the logs of a specific container.

Is there an elegant way to clear these logs?

Docker: How to clear the logs properly for a Docker container?

日志文件

文件系统

服务器

Windows

容器

Docker

Ubuntu

我使用docker logs [container-name]查看特定容器的日志。有没有一种优雅的方法来清除这些日志？

问Docker:如何正确清理Docker容器的日志？
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Docker:如何正确清理Docker容器的日志？EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Docker:如何正确清理Docker容器的日志？
EN