Failed to chmod "MyProject.sh"


Symptoms

Running your Unreal Engine project in Docker fails with the following error:

Running: /usr/bin/env -- "chmod" "+x" "/project/Intermediate/Staging/MultiplayerTest1Server.sh"
chmod: changing permissions of '/project/Intermediate/Staging/MultiplayerTest1Server.sh': Operation not permitted
Took 0.0064401s to run env, ExitCode=1
ERROR: Failed to chmod "/project/Intermediate/Staging/MultiplayerTest1Server.sh"
       (see /home/ue4/Library/Logs/Unreal Engine/LocalBuildLogs/Log.txt for full exception trace)
AutomationTool executed for 0h 2m 46s
AutomationTool exiting with ExitCode=1 (Error_Unknown)
RunUAT ERROR: AutomationTool was unable to run successfully. Exited with code: 1

Explanation

This is happening because there are files in the Intermediate folder that are owned by a different user. This can happen if you build the Linux target on your host machine and then try to run it in Docker.


Solution

Delete the whole Intermediate folder and try again.


Rivet

Open-source multiplayer infrastructure. Easy, flexible, and affordable.

This website is not sponsored by or affiliated with Unity Technologies or its affiliates. Unity Trademark(s) are trademark(s) or registered trademark(s) of Unity Technologies or its affiliates in the U.S. and elsewhere. | This website is not sponsored by, affiliated with, or endorsed by Epic Games, Inc. or its affiliates. 'Unreal Engine' is a trademark or registered trademark of Epic Games, Inc. in the U.S. and elsewhere. | The HTML5 Logo by the World Wide Web Consortium (W3C), used under a Creative Commons Attribution 3.0 License. Source | The Godot Engine Logo by the Andrea Calabró, used under a Creative Commons Attribution 4.0 International License. Source | Docker and the Docker logo are trademarks or registered trademarks of Docker, Inc. in the United States and/or other countries. Docker, Inc. and other parties may also have trademark rights in other terms used herein.

© 2024 Rivet Gaming, Inc. All rights reserved.