Ben, I realised another temporary solution is simply specifying a different value for `tasksDir` under multiuser engine. By default it is /Users but you could change it to e.g. /tasks and that should do the trick (or somewhere else if Big Sur doesn't allow that). The home directory and the task directory are both purged after a task run - if they happen to be the same directory, that is ok, but they don't have to be. For example on Windows, the home directory is typically on C:\ but the task directories are on Z:\ so the multiuser engine is already designed to clean up both after a task. As soon as the task directory moves to a different location, the home directory system files and directories (such as `Library`, `Desktop`, ....) will no longer be in the task directory, so generic-worker won't try to modify their permissions, and the problem goes away. Fingers crossed this should work!
Bug 1673069 Comment 16 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Ben, I realised another temporary solution is simply specifying a different value for `tasksDir` under multiuser engine. By default it is /Users but you could change it to e.g. `/tasks` or `/var/tasks` or something similar and that should do the trick. The home directory and the task directory are both purged after a task run - if they happen to be the same directory, that is ok, but they don't have to be. For example on Windows, the home directory is typically on `C:\` but the task directories are on `Z:\` so the multiuser engine is already designed to clean up both after a task. As soon as the task directory moves to a different location, the home directory system files and directories (such as `Library`, `Desktop`, ....) will no longer be in the task directory, so generic-worker won't try to modify their permissions, and the problem goes away. Fingers crossed this should work!
Ben, I realised another temporary solution is simply specifying a different value for `tasksDir` under multiuser engine. By default it is `/Users` but you could change it to e.g. `/tasks` or `/var/tasks` or something similar and that should do the trick. The home directory and the task directory are both purged after a task run - if they happen to be the same directory, that is ok, but they don't have to be. For example on Windows, the home directory is typically on `C:\` but the task directories are on `Z:\` so the multiuser engine is already designed to clean up both after a task. As soon as the task directory moves to a different location, the home directory system files and directories (such as `Library`, `Desktop`, ....) will no longer be in the task directory, so generic-worker won't try to modify their permissions, and the problem goes away. Fingers crossed this should work!
Ben, I realised another temporary solution is simply specifying a different value for `tasksDir` under multiuser engine. By default it is `/Users` but you could change it to e.g. `/tasks` or `/var/tasks` or something similar and that Big Sur allows. The home directory and the task directory are both purged after a task run - if they happen to be the same directory, that is ok, but they don't have to be. For example on Windows, the home directory is typically on `C:\` but the task directories are on `Z:\` so the multiuser engine is already designed to clean up both after a task. As soon as the task directory moves to a different location, the home directory system files and directories (such as `Library`, `Desktop`, ....) will no longer be in the task directory, so generic-worker won't try to modify their permissions, and the problem goes away. Fingers crossed this should work!
Ben, I realised another temporary solution is simply specifying a different value for `tasksDir` under multiuser engine. By default it is `/Users` but you could change it to e.g. `/tasks` or `/var/tasks` or something similar that Big Sur allows. The home directory and the task directory are both purged after a task run - if they happen to be the same directory, that is ok, but they don't have to be. For example on Windows, the home directory is typically on `C:\` but the task directories are on `Z:\` so the multiuser engine is already designed to clean up both after a task. As soon as the task directory moves to a different location, the home directory system files and directories (such as `Library`, `Desktop`, ....) will no longer be in the task directory, so generic-worker won't try to modify their permissions, and the problem goes away. Fingers crossed this should work!
Ben, I realised another temporary solution is simply specifying a different value for `tasksDir` under multiuser engine. By default it is `/Users` but you could change it to e.g. `/tasks` or `/var/tasks` or something similar that Big Sur allows. The home directory and the task directory are both purged after a task run - if they happen to be the same directory, that is ok, but they don't have to be. For example on Windows, the home directory is typically on `C:\` but the task directories are on `Z:\` so the multiuser engine is already designed to clean up both after a task. As soon as the task directory moves to a different location, the home directory system files and directories (such as `Library`, `Desktop`, ....) will no longer be in the task directory, so generic-worker won't try to modify their permissions, and the problem goes away. Fingers crossed, with this small change, things should just simply work!
Ben, I realised another temporary solution is simply specifying a different value for `tasksDir` under multiuser engine. By default it is `/Users` but you could change it to e.g. `/tasks` or `/var/tasks` or something similar that Big Sur allows. The home directory and the task directory are both purged after a task run - if they happen to be the same directory, that is ok, but they don't have to be. For example on Windows, the home directory is typically on `C:\` but the task directories are on `Z:\` so the multiuser engine is already designed to clean up both after a task. As soon as the task directory moves to a different location, the home directory system files and directories (such as `Library`, `Desktop`, ....) will no longer be in the task directory, so generic-worker won't try to modify their permissions, and the problem goes away. Fingers crossed, with this small change, things should just simply work! Note, we should still implement bug 1673922 and bug 1673992, but changing `tasksDir` should at least unblock using multiuser engine.
Ben, I realised another temporary solution is simply specifying a different value for `tasksDir` under multiuser engine. By default it is `/Users` but you could change it to e.g. `/tasks` or `/var/tasks` or something similar that Big Sur allows. The home directory and the task directory are [both purged](https://github.com/taskcluster/taskcluster/blob/v37.5.1/workers/generic-worker/multiuser.go#L172-L173) after a task run - if they happen to be the same directory, that is ok, but they don't have to be. For example on Windows, the home directory is typically on `C:\` but the task directories are on `Z:\` so the multiuser engine is already designed to clean up both after a task. As soon as the task directory moves to a different location, the home directory system files and directories (such as `Library`, `Desktop`, ....) will no longer be in the task directory, so generic-worker won't try to modify their permissions, and the problem goes away. Fingers crossed, with this small change, things should just simply work! Note, we should still implement bug 1673922 and bug 1673992, but changing `tasksDir` should at least unblock using multiuser engine.