02-21-2018

[JosiahRegencia]

I tested using 172.17.0.2 as the host. It wouldn't stop running.

Thought I'd use the IP of mono_db but apparently it doesn't have one. Wasn't really able to work on a lot. I've been feeling quite feverish today. I'll make up for it.

[JosiahRegencia]

I was more of searching around for solutions but nothing really has come helpful yet

[JosiahRegencia]

https://github.com/mumoshu/kube-airflow/issues/10

Above link might be helpful. I don't really understand what they are saying yet.

[JosiahRegencia]

https://github.com/getsentry/onpremise/issues/32

Above link suggests not to use volumes. Says it's a bug not only on Windows but also on others

[greenmoss]

So you have both the db running via docker-compose, and savant running via docker, right? If so, you should be able to see your listening network interfaces and ports on that system. You can use ip a to see all active interfaces, and ss -ntlp to see ports. I think you should see your 172... address in interfaces, and port 5000 in your ports.

[greenmoss]

The kube-airflow link is for kubernetes, so that won't help us much 😄

[JosiahRegencia]

I guess what I'll try to do initially is to find an alternative to using volumes.

[greenmoss]

Hmm, the reports were on Windows and OS X. On Linux it should be pretty solid.

[greenmoss]

Closing this ticket for work tracking purposes, but we can keep discussing here or on Slack

[JosiahRegencia]

I think it's easier to track the discussion on the ticket rather than on slack. It could be accessed even though it's closed anyway

[greenmoss]

I suspect the curl is to an IP that is not available.

Other than that, the best bet is to check the savant container. Can you ping it? Do logs show a connection attempt (docker logs would show that), or even getting a shell on the container and debugging that way.

[JosiahRegencia]

working on it

[JosiahRegencia]