bug: [PRO] Creating Aurora RDS cluster using Pulumi doesn't use mysql:latest image

[hugo-abhishek]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I am using Pulumi script to create aurora mysql AWS::RDS::Cluster using localstack-pro:latest image. With the older images (localstack-pro:3.4.0) of localstack we noticed mysql:latest images were being used, however, with the latest one's it is using mysql:8.0.28-oracle image.

I am attaching a minimum reproducible code below using Pulumi:
`import pulumi_aws as aws

aws.rds.Cluster("default",
cluster_identifier="aurora-cluster-demo",
engine=aws.rds.EngineType.AURORA_MYSQL,
engine_version="8.0.mysql_aurora.3.04.1",
availability_zones=[
"us-west-2a",
"us-west-2b",
],
database_name="mydb",
master_username="foo",
master_password="bar",
backup_retention_period=5,
preferred_backup_window="07:00-09:00"
)`

Expected Behavior

The later versions of localstack should be using mysql:latest image.

How are you starting LocalStack?

With a docker-compose file

Steps To Reproduce

How are you starting localstack (e.g., bin/localstack command, arguments, or docker-compose.yml)

docker run localstack/localstack

Client commands (e.g., AWS SDK code snippet, or sequence of "awslocal" commands)

awslocal s3 mb s3://mybucket

Environment

- OS:
- LocalStack:
  LocalStack version:
  LocalStack Docker image sha: 
  LocalStack build date:
  LocalStack build git hash:

Anything else?

This version of oracle has some issues during restarts of mysql as mentioned in this [issue](https://github.com/docker-library/mysql/issues/852) and hence we are unable to use it.

[localstack-bot]

Welcome to LocalStack! Thanks for reporting your first issue and our team will be working towards fixing the issue for you or reach out for more background information. We recommend joining our Slack Community for real-time help and drop a message to LocalStack Pro Support if you are a Pro user! If you are willing to contribute towards fixing this issue, please have a look at our contributing guidelines and our contributing guide.

[cloutierMat]

Hi @hugo-abhishek,

For parity with Aurora, we are mapping the version of the mysql engine based on the aurora version configured. As you can see on RDS documentation, 8.0.mysql_aurora.3.04.1 is compatible with 8.0.28.

Furthermore, since the returned engine is mysql:8.0.28-oracle, I assume you are using an ARM CPU. I remember an issue with running non-oracle images on ARM, so all ARM aurora-mysql are currently locked to 8.0.28 with a warning in your LocalStack logs.

I am curious as if there is a reason for wanting to map 8.0.mysql_aurora.3.04.1 to latest instead of the AWS compatible version?

[hugo-abhishek]

Hi @cloutierMat, as mentioned above this version of oracle has issue for chown on broken symlink, this causes subsequent restarts to fail.

This version of oracle has some issues during restarts of mysql as mentioned in this issue and hence we are unable to use it.

The issue was fixed in this PR and it doesn't seem like the image localstack is using has a fix for this. This is the sha for 8.0.28-oracle eb3f4a2767a37c46e2f5424f1f0e8e79ace6fad52400c3220a6b7f7092b52aff.

Upon inspecting the above image, I can confirm above version doesn't contain the fix, and hence the ask for using the latest image (I believe we are fine with any version having this fix)

[cloutierMat]

Thank you @hugo-abhishek for the added context. We will be looking into a fix for this and hopefully be able to pin a version with the appropriate fix while keeping mysql version on par with RDS version compatibility.

In the meantime, I can offer this workaround. You can manually pull the desired image and tag it 8.0.28-oracle on your machine. That way when LocalStack attempts to pull it, Docker will use the one you tagged.

[hugo-abhishek]

Thanks @cloutierMat for the alternate solution.