We recently switched to using docker in our dev environments. One of our dev environment use cases is running some reporting queries using Jupyter notebooks.
However, I can’t figure out a reasonable way to enable a call to
aptible db:tunnel that’s able to be accessed by a running container.
db:tunnelbinds to the loopback interface, it’s not visible to other hosts, including virtualized hosts like a running dev container. I think this is even the case with
hostnetworking, but I’m certainly no pro at this.
It seems a little messy to have folks log into aptible inside a running container (and it’s certainly not as easily scripted). But also, the reliance on ruby 2.2 means that stable releases of debian and ubuntu are out of play, as are our standard docker images (like
So before I go down a path to make a different build process for reporting, I’m wondering if anyone has a setup they like for this kind of thing.