{"version":"2.1.309","anchor":"sandbox-required-failure-message-now-says-dangerouslydisable","canonical_anchor":"sandbox-required-failure-message-now-says-dangerouslydisable","heading":"Sandbox failure error says running outside the sandbox is not allowed either","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/sandbox-required-failure-message-now-says-dangerouslydisable","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Sandbox failure error says running outside the sandbox is not allowed either\n\nWhen a required sandbox fails to start, the error now says dangerouslyDisableSandbox is not allowed either\n\n**What**\n\nThe sandbox limits what commands can reach on your machine. When the sandbox is required but fails to start, the error message used to end with advice to restart or fix your settings. It now adds: \"Running it outside the sandbox (dangerouslyDisableSandbox) is not allowed either.\"\n\n**Why**\n\nWhen the sandbox is mandatory, you learn straight away that `dangerouslyDisableSandbox` will not get the command to run, so you can fix the sandbox instead of retrying without it.\n\n- Area: Sandbox\n- Names: `dangerouslyDisableSandbox`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}