Frappe Bench команда получения ошибок

Question

Я использую образ док-станции Frappe на Linux. Раньше все работало нормально, но сейчас я пытаюсь начать его не работать. Это дает ошибку:

05:28:48 system           | worker_default.1 started (pid=508)
05:28:48 system           | web.1 started (pid=504)
05:28:48 system           | socketio.1 started (pid=505)
05:28:48 system           | worker_long.1 started (pid=501)
05:28:48 system           | watch.1 started (pid=503)
05:28:48 system           | worker_short.1 started (pid=506)
05:28:48 system           | schedule.1 started (pid=507)
05:28:48 socketio.1       | listening on *: 9000
05:28:48 socketio.1       | events.js:167
05:28:48 socketio.1       |       throw er; // Unhandled 'error' event
05:28:48 socketio.1       |       ^
05:28:48 socketio.1       | 
05:28:48 socketio.1       | Error: Redis connection to redis-socketio:12000 failed - getaddrinfo EAI_AGAIN redis-socketio redis-socketio:12000
05:28:48 socketio.1       |     at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:57:26)
05:28:48 socketio.1       | Emitted 'error' event at:
05:28:48 socketio.1       |     at RedisClient.on_error (/home/frappe/frappe-bench/apps/frappe/node_modules/redis/index.js:406:14)
05:28:48 socketio.1       |     at Socket.<anonymous> (/home/frappe/frappe-bench/apps/frappe/node_modules/redis/index.js:279:14)
05:28:48 socketio.1       |     at Socket.emit (events.js:182:13)
05:28:48 socketio.1       |     at emitErrorNT (internal/streams/destroy.js:82:8)
05:28:48 socketio.1       |     at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
05:28:48 socketio.1       |     at process._tickCallback (internal/process/next_tick.js:63:19)
05:28:48 system           | socketio.1 stopped (rc=1)
05:28:48 system           | sending SIGTERM to worker_long.1 (pid 501)
05:28:48 system           | sending SIGTERM to watch.1 (pid 503)
05:28:48 system           | sending SIGTERM to web.1 (pid 504)
05:28:48 system           | sending SIGTERM to schedule.1 (pid 507)
05:28:48 system           | sending SIGTERM to worker_default.1 (pid 508)
05:28:48 system           | sending SIGTERM to worker_short.1 (pid 506)
05:28:48 system           | watch.1 stopped (rc=-15)
05:28:48 system           | schedule.1 stopped (rc=-15)
05:28:48 system           | worker_short.1 stopped (rc=-15)
05:28:48 system           | web.1 stopped (rc=-15)
05:28:48 system           | worker_default.1 stopped (rc=-15)
05:28:48 system           | worker_long.1 stopped (rc=-15)

Может кто-нибудь помочь, как решить эту проблему.