@jeremybarnes , your second suggestion seems like an easy way out. I have ssh access to the remote host, I have installed docker in it. I believe you are talking about establishing a tunnel using ssh. Like on mldb website :
ssh -f -o ExitOnForwardFailure=yes <user>@<remotehost> -L <localport>:127.0.0.1:<mldbport> -N
So, now someone who has access to the remote host will also have access to mldb image that is on my local machine right ?
Now, that I have established a tunnel using ssh, should I use just :
docker run --rm=true \
-v </absolute/path/to/mldb_data>:/mldb_data \
-p 127.0.0.1:<mldbport>:80 \
To access the container from the remote host?
I did exactly that (I even allowed anyone to connect) and I got the following on my shell prompt :
Aborting boot: directory mapped to /mldb_data owned by root
Expected owner uid from MLDB_IDS is: 1001
If the directory mapped to /mldb_data did not exist before launching MLDB,
it is automatically created and owned by root. If this is what happened,
please change the owner of the directory and relaunch.
* /etc/my_init.d/05-mldb-id-mapping.sh failed with status 1
sudo chown $UID.$UID mldb_datain the current directory
KDNuggets Transfer Learning Blog Postwith my own set of images.
inceptionseems that one of the images fails.
try()SQL statement. check the "Handling errors line by line" section here: https://docs.mldb.ai/doc/#builtin/sql/ValueExpression.md.html
Yeah something is definitely not right, when i git checkout v2017.01.24.0 and build MLDB, it runs with no issues: docker run --rm=true -v /home/ubuntu/mldb_data:/mldb_data -e MLDB_IDS="
id" -p 8080:80 quay.io/mldb/mldb:ubuntu-HEAD-5b8653bc2828f1a89e23876e2d05c9a21dd2ed6a
MLDB (version 2017.06.20.dev-5b8653b) is starting up
reading configuration from file: '/etc/mldb.conf'