Auto-Deploy on Push / verify-and-notify (push) Canceled after 0s
Almost every tracked file in the repo had drifted to mode 777 on disk (only files created fresh this session were unaffected), and a chunk of that drift had already been committed as spurious +x bits on plain YAML/Markdown files (authentik.yaml, kustomization.yaml, coturn.yaml, element-server-suite.yaml, TASKS.md, install.md, etc.) - none of these need to be executable. Restored to 644 for regular files, 755 only for actual scripts (postCreateCommand.sh, docker-init.sh, install-hooks.sh, pre-commit hook, element-setup-linux.sh). Also found element-setup-macos.command was missing +x despite having a shebang and being meant for double-click execution on macOS - fixed. Added .gitignore for .DS_Store and .claude/ and stopped tracking the five .DS_Store files that had been committed by accident. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
24 lines
925 B
Bash
Executable File
24 lines
925 B
Bash
Executable File
#!/bin/bash
|
|
# Runs as root at container start (before any `docker exec -u vscode` from VS Code).
|
|
# The docker.sock's GID is only known once the host socket is actually bind-mounted,
|
|
# so it can't be baked in at image build time - it must be reconciled here, at runtime.
|
|
set -e
|
|
|
|
if [ -S /var/run/docker.sock ]; then
|
|
SOCK_GID=$(stat -c '%g' /var/run/docker.sock)
|
|
CURRENT_GID=$(getent group docker | cut -d: -f3)
|
|
if [ -n "$SOCK_GID" ] && [ "$SOCK_GID" != "$CURRENT_GID" ]; then
|
|
EXISTING_GROUP=$(getent group "$SOCK_GID" | cut -d: -f1)
|
|
if [ -n "$EXISTING_GROUP" ]; then
|
|
# GID is already taken by another group (e.g. GID 0/root - Docker Desktop for
|
|
# Mac/Windows owns the socket this way inside its VM), so join that group
|
|
# instead of trying to reassign it to 'docker'.
|
|
usermod -aG "$EXISTING_GROUP" vscode
|
|
else
|
|
groupmod -g "$SOCK_GID" docker
|
|
fi
|
|
fi
|
|
fi
|
|
|
|
exec gosu vscode "$@"
|