existing ezjail conversion process omits many symlink - let's fix that #730
Comments
|
Interesting, I think we can do this simpler. Here's my suggestions: I think that could cover the same usecase with a lot less overhead. Thoughts? |
|
Is this what you mean? 1 - iocage create --basejail -r 12.0-RELEASE -n MyBaseJail |
|
Yes |
|
This assumes we have already completed the steps in "Migrating from Ezjail to Iocage"? |
|
How so? This is all preparatory. You would rsync from the ezjail jail to the iocage jail. Running the iocage jail in step 2 is to make sure the basejail targets for the symlinks are mounted. |
|
I see. It wasn't clear this was all prep. |
|
OK, let's try it: Ahh, yes, let's try devel: Yes, that's better, but I was wrong. |
|
Fixed it: |
|
devel must be older then master, I'm not the ports committer :P Do you have /tmp in a dataset? Or have strict permissions? That file is freebsd-update, just named differently. EDIT: Ignore the couple bugs in the above output, they will be fixed |
|
Step 2: |
|
So this step, unspecified, is not right: |
|
Neither jail is running in your list, which would be a requirement. I didn't say to run rsync directly, I said to take the list from it and sed out the paths. Perhaps do a dry rsync to sed and use cp or something. Not sure |
|
This list will vary from jail to jail and will be dependent upon what is installed in the jail. The list is generated from the rsync. Thus, it must be run by each user, correct? For each jail, right? |
|
I would assume so, that's why I suggested a dryrun of rsync. |
|
This is simpler? ;) |
|
Hahaah perhaps not! |
|
I think this is progress. The following is the difference in symlinks between the original ezjail jail and the copied iocage jail. Let's explain some of those away:
The process was:
Where the list of things to not rsync is: This list is obtained with this command:
Then the prefix '/usr/jails/newjail' is removed from each of those lines. |
|
Sounds like a good script idea hint ;) |
|
I have 66 jails on 6 hosts to convert. Yes, there will be a script of some type. |
|
Heh, make sure you host it for other users! |
|
FYI: There is no reference to thinkconfig in man iocage for Version 1.0 RC 2018/11 |
|
Existing concerns about the script:
Please review and test: https://github.com/dlangille/thin_to_thick |
|
Nice! In your example that's important, as that's not longer a patch level difference but a world difference. I think it's a fair assumption that the users will create the proper RELEASE targets (if it's their first time with iocage then those will be on the latest patch level too) for each of their targets. |
|
I have updated my example, I meant for the release numbers to be the same. However, will the destination jail have issues if the patch levels differ? |
|
That's a pretty wide net to cast an opinion on, unfortunately. I would think it would be pretty minor differences as FreeBSD would typically delay major things for a world change. I wouldn't lose much sleep over it. But if you do, you can always issue an |
Have you considered the sysrc output syntax? It shows before and after. Why? So we know what it was before and that's often useful when adding/updating. I'll raise an issue if you like. |
|
Sure file an issue and I’ll do an enhancement
On Fri, Dec 21, 2018 at 3:22 PM Dan Langille ***@***.***> wrote:
$ sudo iocage set ip4_addr="10.55.0.70" snapshots
Property: ip4_addr has been updated to 10.55.0.70
Have you considered the sysrc output syntax?
It shows before and after.
$ sudo sysrc things=stuff
things: -> stuff
***@***.***:/iocage/jails] $ sudo sysrc things=more
things: stuff -> more
***@***.***:/iocage/jails] $ sudo sysrc -x things
***@***.***:/iocage/jails] $
Why? So we know what it was before and that's often useful when
adding/updating.
I'll raise an issue if you like.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#730 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABg_N3likN-490_6qjRQm9rPzz7aw0Hbks5u7VEwgaJpZM4ZW5F5>
.
--
-Brandon
|
Following https://iocage.readthedocs.io/en/latest/install.html#migrating-from-ezjail-to-iocage the resulting jail works, but it is missing many symlinks. I think I know a way to improve the process.
At present, this issue exists just as a placeholder / discussion point.
My findings:
No action is requested.
Comments and suggestions on the approach are welcome.
Current status: I've identified a possible two step solution and will test it soon:
Make sure to follow and check these boxes before submitting an issue! Thank you.
masterif usinga stable release. N/A
The text was updated successfully, but these errors were encountered: