Docker issue - Error: unable to connect to daemon: context deadline exceeded about mutagen

[jpambrun]

Just in case it's helpful to someone:

> docker info                                                                                                                          Thu 18 Oct 2018 02:22:10 PM EDT
Containers: 1
 Running: 1
 Paused: 0
 Stopped: 0
Images: 16
Server Version: 18.06.1-ce
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 468a545b9edcd5932818eb9de8e72413e616e86e
runc version: 69663f0bd4b60df09991c08812a60108003fa340
init version: fec3683
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.18.12-1-MANJARO
Operating System: Manjaro Linux
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 31.37GiB
Name: desktop
ID: PQLW:QABI:6T3E:NGCZ:ANAT:XJIR:IO2G:L6LS:PRHA:YZMR:GEDI:WT7T
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

[jpambrun]

Some more info, sorry for the spam.
This works:

> cat somefile
sldkjasldjfljlkj
> docker cp somefile nucleus_sync_1:/src
> docker exec -it nucleus_sync_1 cat /src/somefile
sldkjasldjfljlkj
> echo "some pipe test" | docker exec --interactive nucleus_sync_1 /bin/cat -
some pipe test

[xenoscopic]

That error message just means that the Mutagen daemon isn't running. You can start it with the mutagen daemon start command. The Mutagen daemon is sort of analogous to the Docker daemon.

See the "Starting the daemon" section here for additional information.

If the Mutagen daemon is running and you're still seeing this issue, please let me know.

The error message could probably be a bit more helpful. In the future I want to have the daemon automatically start or run as a tray icon on startup, hopefully hiding its existence from the user.

[jpambrun]

Damn.. I did not properly RTFM. That's embarrassing.
I was blindsided by my assumption that docker must have been the issue.

Thanks for the quick response.

[xenoscopic]

No problem. As I said, it's something that users really shouldn't have to worry about, and hopefully it'll be automatic soon.