GitHub Actions
baf822e084
fix: resolve Docker socket permissions and notification page routing
- Add runtime Docker socket permission detection in entrypoint
- Detects socket GID and logs helpful deployment guidance
- Provides three resolution options (root user, group-add, or chmod)
- Non-intrusive: logs only, doesn't modify permissions
- Fix notification page routing mismatch
- Move notifications route from /notifications to /settings/notifications
- Add notifications tab to Settings page with Bell icon
- Align navigation structure with route definitions
- Enhance Docker API error handling
- Return 503 (not 500) when Docker daemon unavailable
- Add DockerUnavailableError type for clear error distinction
- Implement SSRF hardening (reject arbitrary host values)
- Improve security and testability
- Move ProxyHost routes to protected auth group
- Refactor Docker handler tests to use mocks
- Simplify useDocker hook query enablement logic
Docker socket fix addresses deployment-level permission issue without
code changes. The 503 error correctly signals service unavailability
due to configuration, not application bugs.
Closes #XX (if applicable)
2025-12-22 21:58:20 +00:00
..
2025-12-21 21:04:13 +00:00
2025-12-21 22:33:28 +00:00
2025-12-22 21:58:20 +00:00
2025-12-22 04:03:04 +00:00
2025-12-21 04:08:42 +00:00
2025-12-21 04:08:42 +00:00
2025-12-21 04:08:42 +00:00
2025-12-20 20:37:16 +00:00
2025-12-22 01:31:57 +00:00
2025-12-14 00:11:06 +00:00
2025-12-14 00:11:06 +00:00
2025-12-14 00:11:06 +00:00
2025-12-21 04:08:42 +00:00
2025-12-21 04:08:42 +00:00
2025-12-21 04:08:42 +00:00
2025-12-21 04:08:42 +00:00
2025-12-21 22:32:41 +00:00
2025-12-21 23:46:25 +00:00
2025-12-21 04:08:42 +00:00
2025-12-21 04:08:42 +00:00
2025-12-21 04:08:42 +00:00
2025-12-21 04:08:42 +00:00
2025-12-21 04:08:42 +00:00
2025-12-21 04:08:42 +00:00
2025-12-21 19:00:29 +00:00
2025-12-21 23:46:25 +00:00