-
Notifications
You must be signed in to change notification settings - Fork 141
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] "bastille rename" does not update fstab content for Linux container #487
Comments
Hello thanks for report. This should fix the issue: #488 |
Thank you very much! :) |
I can confirm. It's not just a Linux jail issue but for normal ones too. I found that manually editing the fstab to reflect the new directory name can sometimes cause the jail to to start up and then never stop without a full server restart too. That probably should be a separate bug, too. EDIT: My bug was related to this and not Bastille-centric. Carry on |
Hi, yes you are correct, manually editing not only Also the rename command will take care of the Regards |
Since the fix for this got merged, it'd be good to close this issue. |
Bug: When renaming a Linux jail with "bastille rename "target" "new name" the command misses to update the paths located in the fstab file for the jail. If I manually update the paths in the file the jail starts fine.
Bastille and FreeBSD version:
0.9.20211225
13.0-RELEASE-p6
Bastille installed via pkg
Steps:
"mount: /usr/local/bastille/jails/"old jail name": No such file or directory
jail: "new jail name": /sbin/mount -t devfs -o rw devfs /usr/local/bastille/jails/"old jail name"/root/dev: failed
The text was updated successfully, but these errors were encountered: