-
Notifications
You must be signed in to change notification settings - Fork 266
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Others should not access my containers and imges #2
Comments
this part mostly is done in nginx web layer seems in front of real WEB GUI |
Yes, @larrycai . I would like to write some rules of |
These commands work like a charm in my localhost.
If I want to revert it, just run the following commands.
I will update the readme.md for everyone to notice about this 😄 |
Looks quite simple. But I don't fully understand the purpose, do you mean to remove web access probably it is relate to the issues #7 for readonly mode in another machine On Mon, Oct 20, 2014 at 3:40 PM, tobe [email protected] wrote:
True software development embraces consistent inconsistency. |
Currently seagull is designed to monitor docker deamon on arbitrary servers, not just for read-only registry. So if I'm using seagull to monitor my containers, I have to make sure only the authorized IPs can view, start, stop or delete my containers. It can be done by nginx as well and #7 is under consideration. Thanks @larrycai for your suggestion 😺 |
Then why not |
Thanks @larrycai and that's really better. You can send the pull-request to update the notice part in readme.md and readme-zh.md. I will re-open this issue and wait for your contribution 🎉 |
…eter in docker run command to control localhost access
Fixed by @larrycai 's pull-request 👍 |
Now the server is running on localhost and others could access its containers and images. It's not safe for others to start, stop or delete our containers.
The text was updated successfully, but these errors were encountered: