You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dear Author:
Thank you very much for your work. I quickly set up Bookstack using Docker, but I have a question now. I deployed it in CentOS and enabled a policy to restrict access to port 8080 on the firewall, but it did not take effect.
I have looked into it and it may be related to Docker's network. I added the strategy to docker-compose.yml, but it didn't work. Is there any other way?
Thanks you so much.
The text was updated successfully, but these errors were encountered:
Hi,
What are you trying to do?
If you don't want it to be available on port 8080, you can just change the port number before the colon to whatever you want or remove the whole port: block to not publish any ports.
(Though that makes Bookstack completely unavailable.)
Normaly ip/nftables rules for your public interface (typically ethX or enpXsX) should still work, independently of what Docker does.
Dear Author:
Thank you very much for your work. I quickly set up Bookstack using Docker, but I have a question now. I deployed it in CentOS and enabled a policy to restrict access to port 8080 on the firewall, but it did not take effect.
I have looked into it and it may be related to Docker's network. I added the strategy to docker-compose.yml, but it didn't work. Is there any other way?
Thanks you so much.
The text was updated successfully, but these errors were encountered: