{"version":"2.1.318","anchor":"atomic-write-handles-ebusy-on-bind-mounted-files","canonical_anchor":"atomic-write-handles-ebusy-on-bind-mounted-files","heading":"Saving files that are mounted into a container works in more cases","tier":"notice","area":"File Writes","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/atomic-write-handles-ebusy-on-bind-mounted-files","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Saving files that are mounted into a container works in more cases\n\nIf saving over a file mounted into a container fails because it is busy, Claude Code can now write it in place\n\n**What**\n\nClaude Code usually saves a file safely by writing a new copy and then swapping it in for the old one. That swap can fail with a \"busy\" error when the file is bind-mounted, meaning it is a file from another location, such as your computer, mapped into a container. Claude Code now checks the system's list of mounts in `\/proc\/self\/mounts` when this happens. For one particular filesystem type, it then writes straight into the existing file instead.\n\n**Why**\n\nThis lets Claude Code save files that are mapped into containers, where the save could fail before.\n\n- Area: File Writes\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}