Skip to content
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

Closed
drakonkat opened this issue Jan 29, 2025 · 4 comments
Labels
bug Something isn't working

Comments

@drakonkat
Copy link

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

@drakonkat drakonkat added the bug Something isn't working label Jan 29, 2025
@webbertakken
Copy link
Member

Could you share your configuration as well?

@GabLeRoux GabLeRoux changed the title "Shell not foun" on gitlab CI with the new version of "unityci/editor:2022.3.40f1-android-3" "Shell not found" on gitlab CI with the new version of "unityci/editor:2022.3.40f1-android-3" Jan 29, 2025
@GabLeRoux
Copy link
Member

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 ci folder.

One common cause of the shell not found error is the shebang (#!) used in the scripts inside the ci folder. You might want to check and update those to match the latest version. You can find the most up to date scripts here:
🔗 GameCI GitLab CI Scripts

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:
📌 GameCI GitLab CI/CD Example project Releases

Let us know if it works! 🚀

@drakonkat
Copy link
Author

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 :)

@drakonkat
Copy link
Author

Hi,
I resolved the issue, updating the script was ok but mainly the problem was the docker version on the gitlab runner. Actually if you run the runner on docker 19 it will give this error. I understood the problem reading this issue where with different version of docker people has problem with fedora.

So if anyone is here for this issue, i resolved updating docker on the gitlab runner, i hope it can help :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants