investigate whether it's possible that after daemon upgrade there is the same caddy->daemon 502 error as used to be with containers

[gregsadetsky]

saw a 502 api return code suspiciously after a daemon upgrade -- was it the same issue as addressed/fixed in

#68

d3185bb

??