docker.service: 시작 요청이 너무 빨리 반복되어 장치가 실패하는 이유는 무엇입니까?

docker.service: 시작 요청이 너무 빨리 반복되어 장치가 실패하는 이유는 무엇입니까?

내 일기장

The unit docker.service completed and consumed the indicated resources.
мар 05 09:29:56 miki-IdeaPad systemd[1]: docker.service: Start request repeated too quickly.
мар 05 09:29:56 miki-IdeaPad systemd[1]: docker.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit docker.service has entered the 'failed' state with result 'exit-code'.
мар 05 09:29:56 miki-IdeaPad systemd[1]: Failed to start Docker Application Container Engine.
░░ Subject: A start job for unit docker.service has failed
░░ Defined-By: systemd



systemctl status docker.service
× docker.service - Docker Application Container Engine
     Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Tue 2024-03-05 09:29:56 WET; 5min ago
TriggeredBy: × docker.socket

우분투 22.04를 사용하고 있습니다. 도커 정보

Client: Docker Engine - Community
 Version:    25.0.3
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.12.1
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.24.5
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
errors pretty printing info

Docker 포럼에서 많은 게시물을 읽었지만 도움이 되지 않았습니다.

3922 srw-rw----  1 root              docker     0 мар  5 09:29 docker.sock

어떻게 해야 하나요?

관련 정보