-
-
Notifications
You must be signed in to change notification settings - Fork 127
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
"Shell not found" on gitlab CI with the new version of "unityci/editor:2022.3.40f1-android-3" #252
Comments
Could you share your configuration as well? |
Hey there! Upgrading from version 1 to version 3 of the Unity CI Docker images comes with some changes that might be affecting your setup. The example project has been updated to reflect these changes, so you might need to update the scripts in your One common cause of the And if you’d like to see a changelog of recent updates to the CI/CD setup, or subscribe to its changes, you can have a look here: Let us know if it works! 🚀 |
Thanks for the support, maybe i have to update the .sh file in the CI folder, and check the changelog, if this will not work i will share here all the configuration, thanks for the support :) |
Hi, So if anyone is here for this issue, i resolved updating docker on the gitlab runner, i hope it can help :) |
Bug description
I was using the old version "unityci/editor:2022.3.40f1-android-1" and some months ago this disappeared, so i changed it with the version 3 of it "unityci/editor:2022.3.40f1-android-3", but now in gitlab CI i get:
Using docker image sha256:c7815e7a57ade0d3f672ccfe2b351ef2b6f081e2c45c1d13e356193fc82f1d1e for unityci/editor:2022.3.40f1-android-3 with digest unityci/editor@sha256:79df77091f3561949d66dd5397786f019f1c734876ca1d5b9d0f06c288d8125e ... shell not found Cleaning up project directory and file based variables
How to reproduce
Simply follow your tutorial, but with this new version
Expected behavior
Not giving error
Additional details
It's pretty simple, if you have some suggestion i will follow it
The text was updated successfully, but these errors were encountered: