Temporary Unavailability of /mnt/ramdisk for Docker Jobs

Early yesterday we became aware that AWS disclosed three critical vulnerabilities in runc, the open-source component Docker uses to start containers. You can read more here: AWS Security Bulletin. To address these vulnerabilities and protect customer workloads, we applied a security patch across our Docker infrastructure.

As part of that work, the /mnt/ramdisk feature is temporarily unavailable.

Impact
Any jobs using working_directory: /mnt/ramdisk will fail during checkout or workspace attachment steps.

Workaround
Update your config to use the default filesystem instead of /mnt/ramdisk. This change will allow your pipelines to continue running normally.

What’s Next
We’re tracking the upstream runc fix (currently under review here) and will restore /mnt/ramdisk support as soon as it’s safe to do so.These kinds of rapid security patches are rare, and we don’t expect further disruption. We’ll provide an update in this thread once /mnt/ramdisk has been re-enabled.

Thank you for your patience and understanding while we prioritize customer and platform security.

We have identified and applied a workaround for the RAM DIsk issue, which means customers can resume builds using `/mnt/ramdisk`.

We appreciate your patience and understanding whilst we worked on resolving this whilst ensuring the security of our platform for all customers.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.