VM's in FreeNAS 11

[KrisBee]

I'm trying to get a boot2docker VM running or 11RC. I have a NIC and I've added the ISO as a cd-rom, but it doesn't seem to get an IP (nothing in the gui as you can see in the screenshot, and noting in dhcp leases on my router). Any idea how to to give an IP to this VM? What am I doing wrong?
I've also added a screenshot of the 'devices' section of that VM.

Thanks!

I'd be surprised if you'd get a boot2docker VM working via the method you have used. You need to have a clear idea of how boot2docker actually works. AFAIK, you cannot install it from an iso to hard drive and then expect to boot from that hard drive, virtual or real. In any case, at the moment UEFI-CSM in FreeNAS 11RC does not appear to be functioning, and if it was you'd have to connect to serial console.

Zoomzoom's comments are misplaced as boot2docker does not support EFI. See here:
https://github.com/boot2docker/boot2docker/issues/1239

And even if it did, the bhyve UEFI firmware does not behave like the UEFI on a physical machine.

 

[runtime]

I'd be surprised if you'd get a boot2docker VM working via the method you have used. You need to have a clear idea of how boot2docker actually works. AFAIK, you cannot install it from an iso to hard drive and then expect to boot from that hard drive, virtual or real. In any case, at the moment UEFI-CSM in FreeNAS 11RC does not appear to be functioning, and if it was you'd have to connect to serial console.

Zoomzoom's comments are misplaced as boot2docker does not support EFI. See here:
https://github.com/boot2docker/boot2docker/issues/1239

And even if it did, the bhyve UEFI firmware does not behave like the UEFI on a physical machine.

Any chance of support being planned for future?

 

[KrisBee]

Any chance of support being planned for future?

Docker is supposed to return to FreeNAS in some guise at a future date. It can be done now if you are prepared to do the config work manually within a Linux VM, which is the most straightforward route. If can be done now even with boot2docker but is less straightforward and would have to be done via the CLI.

Have a look at this:

https://www.cod3r.com/2017/01/docker-in-freenas-9-10/

But as a word of caution, read this too:

https://forums.freenas.org/index.ph...ding-freenas-corral.53502/page-15#post-371294

 

[runtime]

Docker is supposed to return to FreeNAS in some guise at a future date. It can be done now if you are prepared to do the config work manually within a Linux VM, which is the most straightforward route. If can be done now even with boot2docker but is less straightforward and would have to be done via the CLI.

Have a look at this:

https://www.cod3r.com/2017/01/docker-in-freenas-9-10/

But as a word of caution, read this too:

https://forums.freenas.org/index.ph...ding-freenas-corral.53502/page-15#post-371294

Thanks a lot for the links! I'll set this up when I've got time. I only want to run docker for the select few light services that I need (like the unifi controller and some fancy ui's for rtorrent), I prefer jails for heavier apps, especially since I don't have a lot of resources.

 

[Ziggy]

Have you configured a vLAN adapter on the host [FreeNAS box] for the VM? If not, that must be done, then the vLAN must be assigned to the VM in order for traffic to pass through.

• You can leave the vLAN ID at 0, unless you're already using vLAN tagging, at which point you'll know what number you'll want it's traffic tagged with

Sent from my Nexus 6 using Tapatalk

Thanks zoomzoom. I'm awaiting M0nkey's vid tutorial before starting again. I know too little to proceed, altho I might give it a go in the interim and see if I can apply your advice.

 

[zoomzoom]

Thanks zoomzoom. I'm awaiting M0nkey's vid tutorial before starting again. I know too little to proceed, altho I might give it a go in the interim and see if I can apply your advice.

The IP will be the IP for FreeNAS

Sent from my Nexus 6 using Tapatalk

 

[Ziggy]

Have you configured a vLAN adapter on the host [FreeNAS box] for the VM? If not, that must be done, then the vLAN must be assigned to the VM in order for traffic to pass through.

• You can leave the vLAN ID at 0, unless you're already using vLAN tagging, at which point you'll know what number you'll want it's traffic tagged with

IP is the IP of the FreeNAS box.

Sent from my Nexus 6 using Tapatalk

Ah, so that's the FreeNAS box IP and the port - in the format e.g. 192.168.1.xxx:5900?

 

[FreeNASftw]

Yes. The IP of the FreeNAS box (the same IP you probably type to reach the GUI), and the port listed on the VM page.

 

[Ziggy]

Yes. The IP of the FreeNAS box (the same IP you probably type to reach the GUI), and the port listed on the VM page.

Thanks. I'll give that a go