Open glevner opened 1 month ago
Hm, the Docker image in this repo uses CentOS 7 for Maya 2024, so I expect you'll have more luck trying to install a GCC that is compatible with it instead.
You could also try re-building this image, using the base image used here for Maya 2025, which is Rocky 8. I would expect Maya 2024 to work on Rocky 8 as well.
For example:
The image is based on mottosso/mayabase-centos7, but if you look inside the image, /etc/centos-release
says:
Rocky Linux release 8.7 (Green Obsidian)
What on earth!? Haha, yes I see that. That's.. a bug? 🤔 The other Maya images, e.g. 2022, uses the same base image, and it says:
CentOS Linux release 7.8.2003 (Core)
Someone must have pulled a switcharoo on the base-base image by the time it was created and uploaded to Docker Hub.
In that case, do share any solution you find.
I've tried to build my own Maya 2024 image, starting with mottosso/mayabase-rocky8 instead of mottosso/mayabase-centos7, but I don't have access...
ERROR: failed to solve: mottosso/mayabase-rocky8: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
(mottosso/mayabase-centos7 doesn't work either, but I don't understand why.)
Could you possibly give me access to the mayabase-rocky8 repository, so that I can try building a Maya 2024 image myself?
It's not on Docker Hub, it's right here: https://github.com/mottosso/docker-maya/blob/2025/Dockerfile.mayabase
I contacted Autodesk, and it turns out this is a known issue for Maya 2024. The workaround they suggest is to install gcc-toolset-9 before Maya, and to install Maya with the rpm
options --nodeps
and --force
. I have tested, and that does work.
I am trying to use the maya:2024 Docker image to build a plugin for Maya. I also need gcc 9, which involves installing Rocky Linux's gcc-toolset-9 package. But when I try to install it in my container, I get the following conflict from dnf:
Attempting to install the tcl package results in the same error. And I cannot remove the existing tcl package, because dnf does not think it is installed...