You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In dind-rootless container mode, volume mounts in docker is always mounted as the root user (usermapped to the "runner' (id: 1000) in the ARC runner container. Thusly this requires a workaround:
To get around the fact that we are using a non-root user in the docker container to run the build.
The jenkins user also appears to be some legacy user that was likely used at at time when PyTorch was using Jenkins CI. Post ARC Runner migration when all the jobs are running on ARC we should look into removing the need for this workaround and updating the user where appropriate to remove this legacy configuration.
The text was updated successfully, but these errors were encountered:
No this is a future issue to track the removal of the workaround we put in place. The workaround to chmod stuff was put in place to allow ARC to move forward but I believe it is technical debt which at some point we should find a cleaner solution for that doesn't require so much chowing. It would likely require making some big changes to pytorch build and test code though so I don't expect this issue to be done in the near term.
In dind-rootless container mode, volume mounts in docker is always mounted as the root user (usermapped to the "runner' (id: 1000) in the ARC runner container. Thusly this requires a workaround:
To get around the fact that we are using a non-root user in the docker container to run the build.
The
jenkins
user also appears to be some legacy user that was likely used at at time when PyTorch was using Jenkins CI. Post ARC Runner migration when all the jobs are running on ARC we should look into removing the need for this workaround and updating the user where appropriate to remove this legacy configuration.The text was updated successfully, but these errors were encountered: