-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for ARM64 #343
Support for ARM64 #343
Conversation
I think this is due to compatibility, the assumption being that Maria would be closer to MySQL 5.7 in terms of compat. We will need to switch Altis Cloud to MySQL 8 at some point . I don't believe AWS Aurora MySQL supports 8 yet, so I don't think we'd be switching for some time though. |
That minio error is kinda telling: I think it'll work with a slash on the end eg. https://s3-subdomain.altis.dev/minio/ - if the admin tools menu link is missing that then we should add it. Maybe it's some change in minio 10. Let me know if that sorts it anyway. Maybe some other Minio admin related stuff has changed. |
I'll go through an make tagged releases for anything referencing The MySQL 8 issue seems to be the major hurdle here. Local databases will need to be recreated to use it iirc. We could try this image in the interim https://hub.docker.com/r/biarms/mysql - not official but has a lot of pulls / usage. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should cover it
It did not, same error though there's now a
And correct, the tools menu item doesn't include the trailing slash... |
Thanks, I'll go through and update images in the coming days, I should be able to dump my database and try with that MySQL v5.7 build also. |
Cheers for confirming, will need to dig into the config then. There's a bit of faffing around to get the URLs to play nicely. |
n.b. I made some slight improvements to the Minio/AWS SDK configuration in #341 that might be worth looking at here; in particular, changing the Minio hostname and the SDK config to avoid dynamically building hostnames. |
I noticed in https://github.com/humanmade/altis-local-server/blob/arm64-support-stephen/inc/composer/class-command.php#L706 too we reference a version of minio, does that need to be updated? |
Ok I can confirm I'm working, with all ARM containers (I did some manual fix-ups to the above missing images): I wrote a quick bash script to verify (all
The amd64 one at the end is |
Ah ok, it won't be used unless you pass the What version of the mutagen beta do you have installed? It looks like multiarch builds should be available with the 0.12.0 beta https://hub.docker.com/r/mutagenio/sidecar/tags |
For what it's worth mutagen is still an experimental feature so I don't see that as a blocker for this. |
Yeah, I've been using mutagen locally, unsure how to fully test, but nothing seems to break, latest arm64 links and instructions are in the nightly docs too |
I suspect so, I missed updating this, once minio was bumped to |
@@ -91,7 +91,7 @@ protected function get_php_reusable() : array { | |||
'condition' => 'service_started', | |||
], | |||
], | |||
'image' => 'humanmade/altis-local-server-php:4.0.0-dev', | |||
'image' => 'humanmade/altis-local-server-php:4.2.0', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@roborourke -dev
IIRC is the dev container, not a "dev version" that has xdebug intsalled: https://github.com/humanmade/docker-wordpress-php/blob/master/Dockerfile-dev. Did we stop using -dev
just for the tag (and it's built from -dev
?)-- sorry I can't remember but wanted to check, as I think it might have even been me who made that change!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah gotcha, yeah so the GitHub workflow uses the Dockerfile-dev
file to build. It wasn't a dev container - it was always just used to reference the version that had Xdebug installed. I think that's fine personally as Xdebug 3 can be present and have minimal impact. Plus we don't use the builds on Docker hub on our infrastructure.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't make that particular change, I just didn't notice it earlier - I thought we still had the regular tag and tag + -dev
with Xdebug being built and pushed up.
The -dev
suffix was previously how we toggled between a container with Xdebug and one without, but we use the XDEBUG_MODE
env var to switch it on or off now.
Container versions are all correct now, confirmed working
Follow up to #252
This PR was created using Altis v8 with
local-server
release candidate8.1.0-rc
hereNotes:
latest
for Docker images here for simplicity, pinning to specific releases would be required for releasemysql/mysql-server:8.0
, rather than MariaDB, solely because I have a client project where I'm using this daily, I think the suggestion has been to prefer MariaDB over MySQL v8?Testing
From the dashboard -> tools menu e.g. https://subdomain.altis.dev/wp-admin/tools.php
NoSuchKeyThe specified key does not exist.minios3-subdomain/minious-east-xxxxxxxxxxx