Upgrading SEEK in Docker with MySQL and SOLR in Micro-services

[mbd hki]

Hello Seek Developers,

I hope this message finds you well. I am currently working on upgrading SEEK within a Dockerized environment where MySQL and SOLR are running as separate micro-services using Docker Compose.

I have been following the upgrading process outlined in the documentation, which is similar to upgrading a basic container. However, I've encountered a persistent issue related to the MySQL signature during the upgrade process.

Here are the steps I've followed:

    Update docker-compose.yml for the new SEEK version:

image: fairdom/seek:1.13

Execute the following commands:

    docker-compose down
    docker-compose pull
    docker-compose up -d seek db solr
    docker exec -it seek docker/upgrade.sh
    docker-compose down
    docker-compose up -d

At this point, when I tried to run docker-compose up -d seek db solr I encountered the MySQL signature issue. The error message I received is:

ERROR: missing signature key

I have attempted to refresh GPG keys and import the new key (A8D3785C), but the issue persists

It's worth noting that I am upgrading versions one by one until reaching version 1.13.

If any of you have experienced a similar situation or have insights into resolving MySQL signature issues during SEEK upgrades with Docker Compose, your guidance would be immensely valuable.

Thank you in advance for your assistance.

Kind regards,
Khaled

[mbd hki]

Hello Seek Developers,

I hope this message finds you well. I wanted to provide an update on the MySQL signature issue I encountered during the SEEK upgrade process within a Dockerized environment.

After further investigation, I have found a resolution to the problem. It appears that the issue is not directly related to SEEK but rather to the official MySQL Docker image. When using the official MySQL image, I encountered the "missing signature key" error during the upgrade process.

To resolve this issue, I switched to using an alternative MySQL image, specifically cimg/mysql, and everything worked seamlessly. It seems that the problem lies within the official MySQL Docker image or its compatibility with the SEEK upgrade process.

For your reference, here is the modified section in the docker-compose.yml file:

services:
  db:
    image: cimg/mysql
    # ... other configurations ...

By making this change, I was able to successfully upgrade SEEK to version 1.13 without encountering the MySQL signature issue.

I hope this information proves helpful to anyone facing a similar situation. If you have any further insights or suggestions, feel free to share them.

Thank you for your attention and assistance.

Kind regards,
Khaled