Docker image for amd64

[mariusc23]

Hi, congrats on launching v3! My instance got auto updated by watchtower and I'm getting this error trying to run it on an ubuntu server.

exec /usr/local/bin/docker-entrypoint.sh: exec format error

From some quick googling it might happen due to the docker image architecture not matching the host. Looks like on docker hub only linux/arm64/v8 version is published:
https://hub.docker.com/layers/kutt/kutt/latest/images/sha256-9c1977ba8b71d439dd9e9b5116a53f67742effeee6ab59d3de3cfc84fcb761db

Vs for 2.7.4 there was also a versions for amd64:
https://hub.docker.com/layers/kutt/kutt/v2.7.4/images/sha256-2fa9480755229bd9a14ea03fb2129eb80412600f3c5dabc8f9f9fbf35ff88fce

Thanks!

[jurgenhaas]

Yes, looking at https://hub.docker.com/r/kutt/kutt/tags all previous versions have 3 different images, but v3 only has 1. Maybe the build process failed?

[poeti8]

For some reason npm install hangs on linux/arm/v7 and that fails the whole build.

https://github.com/thedevs-network/kutt/actions/runs/12680476630/job/35343075489

I'm trying to find a fix. If you know what can be done here please let me know.

[poeti8]

I removed platforms from GitHub build for now. I'll add them back once I figure out how to fix the issue for arm64.

[jurgenhaas]

It seems to be an issue with amd84, not arm64, though.

[kaidonato]

Issue closed but I'm facing the same issue still.

[jurgenhaas]

Not sure, why this got closed either. I see there is now the main tag, and that image does work on Linux. But when I created an admin account and then logged in as my user, all my historical data is gone. What do we need to do to migrate that data over?

[AiroPi]

On the release for v3.0.0 there is a migration guide.

[jurgenhaas]

Sure, that states "Merging changes and running the database migration scripts should be enough." and I assume the database migration scripts are running automatically? Because it doesn't tell us what else we should be doing.

[jurgenhaas]

Ah, my bad. I forgot to configure the DB_CLIENT variable. Setting that to pg is required when I want to continue using the previous database. However, this then runs into a migration error which I reported at #779

[poeti8]

Closed this issue because I updated the main build and it should run on amd64 now. If any one still has a problem with amd64 let me know, and I'll reopen this issue.

If any one has problems with migrating to the new version, please send them on #781.

@jurgenhaas I'll look at the issue you created separately.