-
I'm trying to run a ghost blog stack in Portainer CE 2.20.3 and mysql:5.7 which is now depreciated is working fine but mysql:8.0 won't work. The ghost blog application is confirmed working with 8.0 but it won't running as a stack inside Portainer. Here is my compose file:
The version line was removed because Portainer told me it was no longer needed. If I change mysql:8.0 to mysql:5.7 it works every time but any 8.x version will not work. I've tried many, I've also tried latest. Is it just portainer? Can this be fixed/updated in a future update? I don't want to use mysql 5.7. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
What error do you get? I am using Ghost and have it running 8.0 deployed via Portainer just fine. Here is my compose
|
Beta Was this translation helpful? Give feedback.
-
I closed it but it's being shown as unanswered, maybe you can change it to answered. |
Beta Was this translation helpful? Give feedback.
Apologies, didn't update this.
I got it working.
I’m running a Portainer VM on Proxmox and I needed to change my CPU type to host because mysql 8 gives an error if not:
Fatal glibc error: CPU does not support x86-64-v2
Then the database created itself but the ghost container would not start for about 10 minutes because I read it can take time for the database to build itself.
Everything is working now with mysql 8 and the latest ghost. This was my exact issue, hopefully others will find it usual if they're using the same setup. This can be closed/solved.