EDIT: This is scoped to any deletion. Not just symlinks.
Hello,
The Pipelines team has done some investigation into this, and this issue seems to be happening when the following three conditions are met:
- Your account has user namespace remapping enabled. This is currently enabled globally. (This was a security feature we've wanted to enable for a while and significantly improves the security of our build cluster.)
- You are trying to delete a file.
- You are doing the deletion inside of Docker. (With a few additional conditions)
We're still looking for a long term fix for this, but in the meantime you can try the following workarounds:
- Contact Atlassian Support. We'll add you to the whitelist to disable user namespace remapping (please reference this Community question so we can verify you fall into these known conditions).
- Delete the directory or file in the same Docker build instruction as it's created.
An example of the Docker build workaround. Is starting with this (failing) Docker image:
FROM ubuntu:18.04
RUN echo "test" > file1.txt
# Shows file1.txt
RUN ls -l
# Attempt to delete file1.txt
RUN rm file1.txt
# Shows that file1.txt still exists. When it should have been deleted.
RUN ls -l
You can then change it to instead be:
FROM ubuntu:18.04
RUN echo "test" > file1.txt \
&& ls -l \
&& rm file1.txt \
&& ls -l
Sorry for the inconvenience. We're still pinpointing the root cause of this.
@Tania Petsouka, your account has been whitelisted (as mentioned in your support ticket). You should be able to run pipelines again without any other workarounds.
Thanks,
Phil
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.