Why does the Docker image think my instance is not installed yet?

I’m trying to run my existing Nextcloud 12.0.3 test instance using the docker image. I followed the instructions here: https://github.com/nextcloud/docker Well, more, used them as a guideline…

When I try to view the instance, it asks me to create a new admin user.

Shouldn’t it just ask for a normal login when the database and data directory are already populated?

If it thinks my instance is not installed, shouldn’t it also be asking for a database? (It has been a long time since I installed…)

Am I missing a step?

Here is the docker-compose file:

version: '2'

volumes:
  nextcloud:
  nfsdatadir:
    driver: local
    driver_opts:
      type: nfs
      o: addr=<ipaddress>,rw
      device: ":/path/to/data/test"
services:
  app:
    image: nextcloud
    environment:
      - MYSQL_DATABASE=<dbname>
      - MYSQL_USER=<dbuser>
      - MYSQL_PASSWORD=<dbpass>
      - MYSQL_HOST=<remote db host>
      - NEXTCLOUD_DATA_DIR=/srv
      - NEXTCLOUD_TABLE_PREFIX=oc_
    volumes:
      - nextcloud:/var/www/html
      - nfsdatadir:/srv
    ports:
      - 6034:80
    restart: always

My apache 2.4 proxy vhost:

<IfModule mod_ssl.c>
Listen 8443 https
<VirtualHost *:8443>
    ServerAdmin email@example.org
    ServerName nextcloud.blah.ttt
    SSLEngine on
    SSLProxyEngine on
    SSLCertificateFile    <cert path>
    SSLCertificateKeyFile <key path>
    SSLCACertificateFile   <ca path>
    ProxyPreserveHost On
    SSLProxyVerify none
    SSLProxyCheckPeerCN off
    SSLProxyCheckPeerName off
    SSLProxyCheckPeerExpire off
    ProxyPass "/" "http://127.0.0.1:6034/"
    ProxyPassReverse "/" "http://127.0.0.1:6034/"
    RequestHeader set X-Forwarded-Port "8443"
    RequestHeader set X-Forwarded-Proto "https"
</VirtualHost>
</IfModule>

System info:

root@testhost:/# docker --version
Docker version 17.09.0-ce, build afdb6d4
root@testhost:/# docker-compose --version
docker-compose version 1.16.1, build 6d1ac219
root@testhost:/# cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS"

I was able to make it work by using my own Dockerfile to create a custom image that included an instance specific config file.

That said, I’d rather not have to make my own image. Is it possible to do what I want without a custom Dockerfile?