I’ll start with the second issue first. This is due to a change in VirtualBox which I described in this earlier post. The next update of XNAT Vagrant will have the default IP addresses changed to fit within the restricted range VirtualBox now supports.
In the meantime, you can fix this issue at the same time as you fix your second issue. Some script is trying to search the file local.yaml but that file doesn’t exist. I’m not sure why that’s happening because the only references I find to it test for existence before trying to access it, but adding a local.yaml to the configuration you’re running should fix the problem, and adding a local.yaml file in your configuration is how you fix the IP address issue.
Go to the folder for the configuration you’re trying to run. For example, if you’re running xnat-release, go to configs/xnat-release.
Create a file named local.yaml.
Add the following text:
vm_ip: 192.168.56.101
Save the file.
Try running your VM again.
--
Rick Herrick
XNAT Architect/Developer
Computational Imaging Laboratory
Washington University School of Medicine
From:
xnat_di...@googlegroups.com <xnat_di...@googlegroups.com> on behalf of Arthur Goldberg <artgo...@gmail.com>
Date: Wednesday, January 5, 2022 at 6:12 PM
To: xnat_discussion <xnat_di...@googlegroups.com>
Subject: [XNAT Discussion] Running XNAT in a Vagrant Virtual Machine
* External Email - Caution * |
Hello
I'm new to XNAT. Following Running XNAT in a Vagrant Virtual Machine, I tried the quick approach, using Vagrant. I installed VirtualBox & Vagrant. VirtualBox runs and shows XNAT:
--
You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
xnat_discussi...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/xnat_discussion/bd095c55-21ec-4539-b8fe-4705c4850382n%40googlegroups.com.
The materials in this message are private and may contain Protected Healthcare Information or other information of a sensitive nature. If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone or return mail.