access denied error using docker-compose

[Susana Sotelo]

Hi,

I am trying to set up INCEpTION using docker-compose and the YAML config file as suggested in the documentation. After running 'docker-compose up', the inception container keeps restarting in an infinite loop (while mariadb is up and healthy).

# docker ps -a
CONTAINER ID        IMAGE                             COMMAND                  CREATED             STATUS                         PORTS               NAMES
44b03b4b3fbb        inceptionproject/inception:23.4   "/bin/sh -c 'java ${…"   11 minutes ago      Restarting (1) 5 seconds ago                       inception-app-1
a11d52465c92        mariadb:10.7                      "docker-entrypoint.s…"   11 minutes ago      Up 11 minutes (healthy)        3306/tcp            inception-db-1

Log errors point to invalid password.

2022-05-29 15:43:53 ERROR [SYSTEM] HikariPool - HikariPool-1 - Exception during pool initialization.
java.sql.SQLInvalidAuthorizationSpecException: Could not connect to address=(host=db)(port=3306)(type=master) : (conn=4) Access denied for user 'inception'@'172.23.0.3' (using password: YES)

(...)

2022-05-29 15:43:53 ERROR [SYSTEM] LiquibaseLockManager - Unable to list Liquibase locks:
java.sql.SQLInvalidAuthorizationSpecException: Could not connect to address=(host=db)(port=3306)(type=master) : (conn=4) Access denied for user 'inception'@'172.23.0.3' (using password: YES)

Versions:

Docker version 19.03.15, build 99e3ed8919
Docker Compose version v2.5.1

OS: Debian 9

Any idea?

Regards,

[Richard Eckart de Castilho]

Hi,

> On 29. May 2022, at 18:11, Susana Sotelo <sdo...@gmail.com> wrote:
>
> I am trying to set up INCEpTION using docker-compose and the YAML config file as suggested in the documentation. After running 'docker-compose up', the inception container keeps restarting in an infinite loop (while mariadb is up and healthy).

Do you specify additional DB settings/credentials in the config file?
If you use the docker compose, it should already handle the DB settings itself and no separate settings should be in the config file.

Btw - which YAML config file? I believe the documentation should speak about "settings.properties" everywhere as the config file. While it is possible these days to have a "settings.yaml", that features is documented nowhere as far as I remember...?

-- Richard

[Susana Sotelo]

Hi Richard,

thanks for your answer.

Sorry, I was not clear with "YAML config file". I was referring to the docker compose script included in the documentation.

https://inception-project.github.io/releases/23.0.1/docs/admin-guide.html#_docker_compose

I just wrote the YAML script and ran docker compose, but it fails as described in my previous mail.

I wonder if the password is set to 'inception'@'localhost' and not 'inception'@'%', hence the error "Access denied for user 'inception'@'172.23.0.3'". I am not very fluent with docker and I don't know how to test it.

Regards,

[Susana Sotelo]

Hi again,

I tried the same on my personal laptop (Debian 11, Docker version 20.10.16, build aa7e414, docker-compose version 1.25.0) and it works like a charm, so I guess the problem is related to the docker version.

Regards,

[Richard Eckart de Castilho]

Hi,

> On 30. May 2022, at 11:36, Susana Sotelo <sdo...@gmail.com> wrote:
>
> I tried the same on my personal laptop (Debian 11, Docker version 20.10.16, build aa7e414, docker-compose version 1.25.0) and it works like a charm, so I guess the problem is related to the docker version.

At least it sounds like it is a problem specific to your initial environment.

As far as I can tell, it should also work with docker-compose version 1.24.1.

If you find out more, please let us know. Maybe we need to add a minimum docker
version information in the documentation.

Cheers,

-- Richard

[Susana Sotelo]

Hi,

it definitely was a problem related with some specific configuration in that server. I tested different versions in other computers (even with the same OS and docker version) and worked fine:

Debian 9 + docker 19.03.15, build 99e3ed8919 + docker-compose version 1.22.0, build f46880fe

Ubuntu 16.04 + docker 20.10.7, build f0df350 + docker-compose version 1.25.0, build 0a186604

Debian 10 + docker 20.10.16, build aa7e414 + docker-compose version 1.25.0, build 0a186604

Thanks again for your help.

Cheers,

Susana