1565919c87
Group membership is fixed at login, so removing (or adding) the docker group does not take effect in the running session. The existing-user migration and the Setup > Security toggles now call `omarchy-state set reboot-required`, so omarchy-update-restart prompts for the reboot that actually applies the change (and the bar shows it pending). A plain log out and back in still works. The migration test now exercises the real removal command and omarchy-state rather than a stub, asserting the reboot flag is set on removal and left alone when the user is already out of the group. Claude-Session: https://claude.ai/code/session_01Gb7x6poap4hGCndPx5qt5T Co-authored-by: David Heinemeier Hansson <david@hey.com> Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
26 lines
947 B
Bash
Executable File
26 lines
947 B
Bash
Executable File
#!/bin/bash
|
|
|
|
# omarchy:summary=Disable sudoless Docker by removing your user from the docker group
|
|
# omarchy:requires-sudo=true
|
|
|
|
set -e
|
|
|
|
if ! id -nG "$USER" 2>/dev/null | grep -qw docker; then
|
|
echo "Sudoless Docker is not enabled: $USER is not in the docker group."
|
|
exit 0
|
|
fi
|
|
|
|
echo "Removing $USER from the docker group..."
|
|
sudo gpasswd -d "$USER" docker >/dev/null
|
|
|
|
# Group membership is fixed at login, so the running session keeps its docker
|
|
# access until it ends. Flag a reboot so omarchy-update-restart prompts for one
|
|
# (and the bar shows it pending); a plain log out and back in works too.
|
|
omarchy-state set reboot-required
|
|
|
|
echo ""
|
|
echo "Sudoless Docker DISABLED. Reboot (or log out and back in) for the change to take effect."
|
|
echo "Docker access now goes through a polkit/sudo prompt again: the Docker TUI"
|
|
echo "(Super + Shift + D) and the Windows VM will ask when they need it, and the"
|
|
echo "plain 'docker' CLI runs under sudo."
|