Fork me on GitHub
#leiningen
<
2018-07-29
>
michaelr10:07:57

lein deps is stuck here

michaelr10:07:12

for 10 minutes and then prints out this message:

michaelr10:07:49

any idea what this could be?

gfredericks10:07:54

what does ping do?

michaelr10:07:27

seems to ping fine

gfredericks10:07:48

and I assume you've done lein deps more than once and it does the same thing?

gfredericks10:07:07

I've never seen that before ¯\(ツ)

michaelr10:07:20

and it only happens on the server.. in my development machine it's fine

gfredericks10:07:39

the ping was from the server too, right?

Alex Miller (Clojure team)10:07:49

Sometimes it helps to lein pom then do mvn -X -e deps as the error msgs are usually better

michaelr10:07:50

thanks. will try that.

michaelr10:07:54

must be somehow related to the environment.. just noticed that the docker image is based on ubuntu 12. will try to use a more recent distribution

gfredericks11:07:05

I guess curl would be another data point

michaelr11:07:26

I narrowed it down to being some issue with DNS resolution within docker

michaelr11:07:39

Nothing to do with lein apparently 🙂

gfredericks11:07:51

and yet ping within docker worked?

michaelr11:07:37

I ran it on the host, not inside docker 🙂

gfredericks11:07:24

okay that makes me feel a little better then

michaelr12:07:18

issue solved by creating a /etc/docker/daemon.json file, like described here: https://askubuntu.com/a/790778

michaelr12:07:33

previously passed the same options using /etc/default/docker