![](http://content.invisioncic.com/u329766/set_resources_34/84c1e40ea0e759e3f1505eb1788ddf3c_pattern.png)
t-mac_003
-
Posts
4 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by t-mac_003
-
-
17 hours ago, John_M said:
The path names are hard coded. If you are not using the default locations for domains (/mnt/user/domains) and appdata (/mnt/user/appdata) or if you call the container anything other than the default (case-sensitive) 'macinabox' the script will fail. So either make sure everything is as the default or edit the script accordingly.
Oh I did not know they were hard coded.
It was not mentioned in the Youtube video or maybe I missed it.
I am using custom paths. I will try to go through the script and update it.
Hopefully it works!
Thanks!
-
[Support] SpaceinvaderOne - Macinabox
in Docker Containers
Posted
@John_M @SpaceInvaderOne
So it seems like when the script is generated, for some reason it does not capture the custom path location of Docker. In my case, I am not using appdata but instead using Docker.
After making manual changes to the script, it ran perfectly fine and added the VM.
There maybe a bug with how the script is generated and it not capturing the changes from the Docker template.
Another thing I noted is that it has to be "system" and not "System" for the custom_ovmf folder location else the VM won't start. The directory location in UnRaid is case sensitive.
@arch1mede
I am not sure why the default path would be an issue but check the script and make sure the paths make sense.