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
I was just exploring data mounts and some thing like this
unshare -m -- /bin/sh -c "mount -o bind,noexec,nosuid,nodev /var/bocker/shared '$btrfs_path/$uuid'/var/www/data"
seems to work well enough for basic host to container mounts.
Apart from iptables, socat is also a excellent option for port forwarding with a simple one liner;
socat TCP-LISTEN:80,fork TCP:10.0.0.2:80
The text was updated successfully, but these errors were encountered:
However, socat is a user space binary. iptables allow for kernel tcp rewriting, which in the long run is what containers need (like brawndo!)
Sorry, something went wrong.
No branches or pull requests
I was just exploring data mounts and some thing like this
unshare -m -- /bin/sh -c "mount -o bind,noexec,nosuid,nodev /var/bocker/shared '$btrfs_path/$uuid'/var/www/data"
seems to work well enough for basic host to container mounts.
Apart from iptables, socat is also a excellent option for port forwarding with a simple one liner;
socat TCP-LISTEN:80,fork TCP:10.0.0.2:80
The text was updated successfully, but these errors were encountered: