Logs was flooded through with this kind of messages (journalctl view):
Feb 14 02:27:20 dwellers.nasqueron.org dockerd-current[7502]: [96B blob data]
Feb 14 02:27:20 dwellers.nasqueron.org dockerd-current[7502]: [102B blob data]
Feb 14 02:27:20 dwellers.nasqueron.org dockerd-current[7502]: [102B blob data]
Feb 14 02:27:20 dwellers.nasqueron.org dockerd-current[7502]: [93B blob data]
I was checking /var/log/messages, which contains these blob data:
[34;40mverb#033[0m #033[35mnode symlink#033[0m /usr/bin/node#033[K#015[#033[90m..................#033[0m] \ : #033[34;40mverb#033[0m #033[35mnode symlink#033[0m /usr/bin/node#033[K#015[#033[90m..................#033[0m] \ : #033[34;40mverb#033[0m #033[35mnode symlink#033[0m /usr/bin/node#033[K#015[#033[90m..................#033[0m] \ : #033[34;40mverb#033[0m #033[35mnode symlink#033[0m /usr/bin/node#033[K#015[#033[90m..................#033[0m] \ : #033[34;40mverb#033[0m #033[35mnode symlink#033[0m /usr/bin/node#033[K#015[#033[90m..................#033[0m] \ : #033[34;40mverb#033[0m #033[35mnode symlink#033[0m /usr/bin/node#033[K#015[#033[90m..................#033[0m] \ : #033[34;40mverb#033[0m #033[35mnode symlink#033[0m /usr/bin/node#033[K#015[#033[90m..................#033[0m] \ : #033[34;40mverb#033[0m #033[35mnode symlink#033[0m /usr/bin/node#033[K#015[#033[90m..................#033[0m] \ : #033[34;40mverb#033[0m #033[35mnode symlink#033[0m /usr/bin/node#033[K#015[#033[90m..................#033[0m] \ : #033[34;40mverb#033[0m #033[35mnode symlink#033[0m /usr/bin/node#033[K#015[#033[90m..................#033[0m] \ : #033[34;40mverb#033[0m #033[35mnode symlink#033[0m /usr/bin/node#033[K#015[#033[90m..................#033[0m] \ : #033[34;40mverb#033[0m #033[35mnode symlink#033[0m /usr/bin/node#033[K#015[#033[90m..................#033[0m] \ : #033[34;40mverb#033[0m #033[35mnode symlink#033[0m /usr/bin/node#033[K#015[#033[90m..................#033[0m] \ : #033[34;40mverb#033[0m #033[35mnode symlink#033[0m /usr/bin/node#033[K#015[#033[90m..................#033[0m] \ : #033[34;40mverb#033[0m #033[35mnode symlink#033[0m /usr/bin/node#033[K#015[#033[90m..................#033[0m] \ : #033[34;40mverb#033[0m #033[35mnode symlink#033[0m /usr/bin/node#033[K#015[#033[90m..................#033[0m] \ : #033[34;40mverb#033[0m #033[35mnode symlink#033[0m /usr/bin/node#033[K#015[#033[90m..................#033[0m] \ : #033[34;40mverb#033[0m #033[35mnode symlink#033[0m /usr/bin/node#033[K#015[#033[90m..................#033[0m] \ : #033[34;40mverb#033[0m #033[35mnode symlink#033[0m /usr/bin/node#033[K#015[#033[90m..................#033[0m] \ : #033[34;40mverb#033[0m #033[35mnode symlink#033[0m /usr/bin/node#033[K#015[#033[90m..................#033[0m] \ : #033[34;40mverb#033[0m #033[35mnode symlink#033[0m /usr/bin/node#033[K#015[#033[90m..................#033[0
It has been identified to come from the etherpad container.
I've relaunched it with --log-driver none to stop the flood, but we'll need in the future to get back Etherpad logging information to debug crashes and data corruption issues (when one occurs, priority should be set to high).