-
Notifications
You must be signed in to change notification settings - Fork 31
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
[BUG] Pot prepare is broken in pot 0.11 #88
Comments
Thanks for reporting. While here, I'm going to add the -S option for the network stack to |
Tests are successful, I'm preparing a fix release. |
The bugfix added a new bug. A pipe at the end of the line is missing causing two grep calls to be combined into one grep call with the arguments of both. |
Describe the bug
Pot 0.11 introduced the new 'pot.stack' parameter to jail configurations. Pot prepare creates a jail 'pot.conf' with two 'pot.stack=ipv4' lines breaking
pot start $jail
. It doesn't create the epair interface required to attach the jail to the public bridge.To Reproduce
Steps to reproduce the behavior:
ifconfig -l
.ifconfig -l
on the host.fgrep pot.stack $jail_pot_conf | wc -l
on the jail pot.conf. It returns two instead of the expected single line.Expected behavior
Pot prepare should continue to work like it did in pot 0.10. It should create a epair, add one end to the bridge and pass the other end to the jail's network stack. Extending the new support for IPv6 and IPv6+IPv4 to prepared jails would be nice to have.
The text was updated successfully, but these errors were encountered: