Софт
   383

Не работает Docker

Пробую версии из реп и из AUR'a, результат один:

sudo systemctl status docker
● docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor prese
   Active: failed (Result: exit-code) since Mon 2017-01-30 15:46:53 MSK; 13s ago
     Docs: https://docs.docker.com
  Process: 3109 ExecStart=/usr/bin/dockerd -H fd:// (code=exited, status=1/FAILU
 Main PID: 3109 (code=exited, status=1/FAILURE)
    Tasks: 0 (limit: 4915)
   Memory: 2.1M
      CPU: 54ms
   CGroup: /system.slice/docker.service

янв 30 15:46:52 strannik-desktop systemd[1]: Starting Docker Application Contain
янв 30 15:46:52 strannik-desktop dockerd[3109]: time="2017-01-30T15:46:52.968753
янв 30 15:46:53 strannik-desktop dockerd[3109]: time="2017-01-30T15:46:53.977480
янв 30 15:46:53 strannik-desktop dockerd[3109]: time="2017-01-30T15:46:53.977895
янв 30 15:46:53 strannik-desktop systemd[1]: docker.service: Main process exited
янв 30 15:46:53 strannik-desktop systemd[1]: Failed to start Docker Application 
янв 30 15:46:53 strannik-desktop systemd[1]: docker.service: Unit entered failed
янв 30 15:46:53 strannik-desktop systemd[1]: docker.service: Fail


sudo docker run hello-world
docker: An error occurred trying to connect: Post http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/create: read unix @->/var/run/docker.sock: read: connection reset by peer.

ls -l /var/run/docker.sock 
srw-rw---- 1 root docker 0 янв 30 15:48 /var/run/docker.sock

sudo docker daemon -H tcp://0.0.0.0:4243 -H unix:///var/run/docker.sock
WARN[0000] [!] DON'T BIND ON ANY IP ADDRESS WITHOUT setting -tlsverify IF YOU DON'T KNOW WHAT YOU'RE DOING [!] 
INFO[0000] libcontainerd: new containerd process, pid: 4971 
WARN[0000] containerd: low RLIMIT_NOFILE changing to max  current=1024 max=4096
ERRO[0001] [graphdriver] prior storage driver "btrfs" failed: prerequisites for driver not satisfied (wrong filesystem?) 
FATA[0001] Error starting daemon: error initializing graphdriver: prerequisites for driver not satisfied (wrong filesystem?) 


Что делать?

0 комментариев

Только зарегистрированные и авторизованные пользователи могут оставлять комментарии.