ECS Deployment Failing about shlink-docker-image HOT 9 CLOSED

I believe the best solution is a script to check if the database exists with tables and if so then don't try to re-init everything.

from shlink-docker-image.

@BitForger both latest and v1.15.1 are now being rebuilt with the fix applied. They should be ready in 30min-1hour (probably less, but docker hub is slow building images, so just in case).

from shlink-docker-image.

Yep, you are probably right.

The operations run in the entry point should be more granular, in order to avoid trying to recreate the database when it already exists.

I will try to provide a fix.

from shlink-docker-image.

Yep, you are probably right.

The operations run in the entry point should be more granular, in order to avoid trying to recreate the database when it already exists.

I will try to provide a fix.

I should note that it seems to be an issue because I'm using an RDS running MariaDB. I tried to replicate it locally and it seems fine starting up and stopping using the local SQLite implementation.

from shlink-docker-image.

Yes, the problem will happen only when using an external database, because when using the sqlite one, a new database is created every time you create a container, so it doesn't fail.

If you try to use an existing database with a new container, you will see the error.

from shlink-docker-image.

Yep, that's what I had in mind :)

from shlink-docker-image.

I'm writing something in PHP right now, I'll send it over when I'm done.

from shlink-docker-image.

I'm seeing another issue when trying to redeploy using my own copies.. if it happens in those builds i'll open another ticket.

from shlink-docker-image.

I have just checked that both builds have finished successfully. You should be able to pull both latest and v1.15.1 with the new entry point.

from shlink-docker-image.