[GH-ISSUE #201] Enhance the socket security #175

New issue

Closed

opened 2026-02-26 06:31:09 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 06:31:09 +03:00

Owner

Originally created by @burntoc on GitHub (Sep 18, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/201

Does this support the techniques that the jwilder image references regarding exposing a separate container so that you don't have the docker socket bound to a publicly exposed container service? If not, can it be made to somehow in the interest of additional security?

Originally created by @burntoc on GitHub (Sep 18, 2019). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/201 Does this support the techniques that the jwilder image references regarding exposing a separate container so that you don't have the docker socket bound to a publicly exposed container service? If not, can it be made to somehow in the interest of additional security?

kerem

2026-02-26 06:31:09 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-02-26 06:31:11 +03:00

Author

Owner

@jc21 commented on GitHub (Nov 7, 2019):

I'm confused. This project, or at least the recommended usage of it, doesn't mount or make use of the Docker Socket file from the host.

@jc21 commented on GitHub (Nov 7, 2019): I'm confused. This project, or at least the recommended usage of it, doesn't mount or make use of the Docker Socket file from the host.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#175

No description provided.

Rows
Columns