{"version":"2.1.248","anchor":"background-daemon-refuses-to-start-without-a-usable-uid-mapp","canonical_anchor":"background-daemon-refuses-to-start-without-a-usable-uid-mapp","heading":"Background daemon refuses to start without a usable uid mapping","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/background-daemon-refuses-to-start-without-a-usable-uid-mapp","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Background daemon refuses to start without a usable uid mapping\n\nThe background daemon refuses to start when a namespace collapses all users to one id.\n\n**What**\n\nOn Linux and macOS, the daemon start path now checks first for a user-namespace setup where every user collapses to the same id, and refuses to start with cause `uid_collapse` plus guidance to start with a uid map or pass a socket path explicitly. Windows skips the check entirely.\n\n**Details**\n\n- Returns a failure result and records a telemetry event rather than launching and failing later.\n\n**Evidence**\n\n`daemon_ensure_running`\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}