I don't really learn much 🤷🏻♂️ even though i log in with my root user and create the vm, truenas still don't give the vm application read access to the network share that downloaded the iso. I get it; docker containers needs this safety in order to keep data safe from breaced software but built in VM software specifically started under rooot user? That's a restraining amount of safety
Start Your Containers with host network mode. This will allow them access to the network through the host. Bridged is also another option. Depending on your network setup and unique needs, you should be able to do quite a bit.
@CoffeeEngineerOfficial no the network share is a part of the same truenas host I'm trying to have the VM on. I don't know if I'm making any sense here.
@@RealGengarTV If you cannot communicate to the host machine on the VM level, try accessing it via a bridge. So I bridged the single port, then I was able to access the host's network shares.
@@CoffeeEngineerOfficial I've fixed it. Here's my solution; I used to run a VM in TN core, switched to scale. TN core made a folder called (name of main pool)/VM where VM's are stored, i took this folder, made it a hidden share and gave full read/wright/execution rights to the share in the vm application in users
Awesome video! Your fix for the setup issue worked like a charm. Subscribed! 👍
Well done from your great uncle from Zimbabwe
I don't really learn much 🤷🏻♂️ even though i log in with my root user and create the vm, truenas still don't give the vm application read access to the network share that downloaded the iso. I get it; docker containers needs this safety in order to keep data safe from breaced software but built in VM software specifically started under rooot user? That's a restraining amount of safety
Start Your Containers with host network mode. This will allow them access to the network through the host. Bridged is also another option. Depending on your network setup and unique needs, you should be able to do quite a bit.
@CoffeeEngineerOfficial no the network share is a part of the same truenas host I'm trying to have the VM on. I don't know if I'm making any sense here.
I'm thinking maybe I need to create a dataset specifically for the VM software user 🤔 as I said, this is a restraining amount of safety
@@RealGengarTV If you cannot communicate to the host machine on the VM level, try accessing it via a bridge. So I bridged the single port, then I was able to access the host's network shares.
@@CoffeeEngineerOfficial I've fixed it. Here's my solution; I used to run a VM in TN core, switched to scale. TN core made a folder called (name of main pool)/VM where VM's are stored, i took this folder, made it a hidden share and gave full read/wright/execution rights to the share in the vm application in users