We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
are these subnet and gateway as example ? as it looks not real IPs , and what should it be any private subnet or related to the local machine.
Also what the full command of the Firwall, also is reverse proxy is mandatory ?
docker network create -d macvlan -o macvlan_mode=bridge --subnet=111.222.333.443/29 --gateway=111.222.333.444 -o parent=eth1 macvlan_bridge
The text was updated successfully, but these errors were encountered:
Yes, they are examples, I wouldn't have my real IP posted.
Any default install of Docker does not have any ports or IPs public open/accessable. So you need to have network setup or how to knowledge.
I have physical/rented remote server that I have public IPs to access.
I really can't help cause this is really not plug in play as far as networking, which seems like what you asking.
Sorry, something went wrong.
No branches or pull requests
are these subnet and gateway as example ? as it looks not real IPs , and what should it be any private subnet or related to the local machine.
Also what the full command of the Firwall, also is reverse proxy is mandatory ?
docker network create -d macvlan
-o macvlan_mode=bridge
--subnet=111.222.333.443/29
--gateway=111.222.333.444
-o parent=eth1 macvlan_bridge
The text was updated successfully, but these errors were encountered: