Problem with building a Docker container

[MKleusberg]

I just tried to build a Docker image by running

cd path/to/dbhub.io/docker
docker build .

and I got this error message:

[...]
Step 21/27 : RUN mkdir -p /go/src/github.com/sqlitebrowser &&     cd /go/src/github.com/sqlitebrowser &&     git clone https://github.com/sqlitebrowser/dbhub.io &&     cd /go/src/github.com/sqlitebrowser/dbhub.io &&      /go/bin/dep ensure &&     go build -gcflags "all=-N -l" -o /usr/local/bin/dbhub-webui github.com/sqlitebrowser/dbhub.io/webui &&     go build -gcflags "all=-N -l" -o /usr/local/bin/dbhub-db4s github.com/sqlitebrowser/dbhub.io/db4s
 ---> Running in 1aa80928fbf2
Cloning into 'dbhub.io'...
could not find project Gopkg.toml, use dep init to initiate a manifest
The command '/bin/sh -c mkdir -p /go/src/github.com/sqlitebrowser &&     cd /go/src/github.com/sqlitebrowser &&     git clone https://github.com/sqlitebrowser/dbhub.io &&     cd /go/src/github.com/sqlitebrowser/dbhub.io &&      /go/bin/dep ensure &&     go build -gcflags "all=-N -l" -o /usr/local/bin/dbhub-webui github.com/sqlitebrowser/dbhub.io/webui &&     go build -gcflags "all=-N -l" -o /usr/local/bin/dbhub-db4s github.com/sqlitebrowser/dbhub.io/db4s' returned a non-zero code: 1

Can you point me in the right direction, @justinclift?

Also wondering if the the last line of the Dockerfile should have 443 instead of 8443 or if this is on purpose because it's running locally?

EXPOSE 8443 5550 9000 40000

[scottfurry]

Wild stab in the dark...
cd /go/src/github.com/sqlitebrowser/dbhub.io && /go/bin/dep ensure
is what is failing. Ideally, there should be a cd [path] || die in there. Check paths and permissions.
IIRC, 443 is the SSL port number? Again, idle observation.

[justinclift]

Oops. I haven't even looked at the docker stuff for DBHub.io in ages. The docker pieces have likely bitrotted. 😉

The error message:

could not find project Gopkg.toml, use dep init to initiate a manifest

Is from the old Go dependency manager, dep, which we no longer use. The DBHub.io repo moved to using Go modules (the official Go dependency manager approach) instead. But our docker pieces haven't been updated to match.

I'll need to take a look at the Docker pieces again, to get it working.

Depending on your goal, you could skip using Docker and set things up manually. Memcached, and PostgreSQL can likely be installed from your system package manager (apt, yum, etc). The Minio server is a single file executable that can be run from anywhere. Hmmm... methinks I'd better document the manual setup.

[MKleusberg]

Oh ok 😄 I'm not really interested in using Docker anyway. So I'll try the manual setup as soon as there's some document 😄 No need to hurry though - I was just wondering how this looks like from the server side.

[justinclift]

No worries. I'll write something up over the next few weeks. 😄

[MKleusberg]

Just started working through this again today. I think I made some good progress towards running the dbhub services locally 😄 @justinclift Could you maybe update the certificates in db4s/certs though? I'm getting error messages because they expired in 2019 and I'm not sure if I should completely regenerate them myself or ping you instead 😉

[justinclift]

No worries, looking at it now. 😄

[justinclift]

@MKleusberg Just to double check, you're definitely meaning the certs in db4s/certs yeah? Asking because they seem to have expired in 2018 (heh).

So, they definitely need updating (which I'm refreshing my memory of how to do 😉). But asking just in case something is strange, as you mention 2019. (?)

[MKleusberg]

Oh you're right. I definitely meant those but didn't look close enough 😉

[MKleusberg]

Oh no, I meant the ones in docker/certs afterall. Sorry about the confusion! 😄

[justinclift]

Just pushed a new commit with a regenerated db4s-dev.dbhub.io certificate. I tend to put that name in my local /etc/hosts file, pointing to (say) localhost or a local dev VM (etc).

[justinclift]

Oops. k, gimme a minute. I'll regenerate the docker ones too. 😉

[MKleusberg]

Thanks! It turned out that I still had that name in my /etc/hosts from years ago. So that was no problem.

One more thing I noticed: I had to add this to the config file to fix the login.

diff --git a/docker/config.toml b/docker/config.toml
index 58a5312..a138138 100644
--- a/docker/config.toml
+++ b/docker/config.toml
@@ -10,6 +10,7 @@ directory = "/home/dbhub/.dbhub/disk_cache"
 
 [environment]
 environment = "docker"
+user_override = "default"
 
 [event]
 delay = 2

Not sure if default is the right name here. I just chose it for simplicity.

[justinclift]

Just pushed an updated docker certificate too. 😄

Good point about the new user_override setting needed in the config file too. It's purpose is to bypass the Auth0 authentication piece, which can be a bit of a pain when doing (local) development. Especially when travelling or with limited internet access.

The username in there just needs to match a valid username in your local development DBHub.io database, as you'll be effectively logged in as that user. I don't remember off hand if there's a default one, but I guess you'll be finding out soon. 😛