Thanks Ron. Thinking my requirements through again, I’ve decided to scrap the iSCSI mount and use NFS/CIFS instead. So following your pointer I have NFS mounted in the host, and then bind-mounted that to the container. I’ve yet to see how that migrates, but one bridge at a time!
Thanks again. Kind regards Ed From: lxc-users [mailto:lxc-users-boun...@lists.linuxcontainers.org] On Behalf Of Ron Kelley Sent: 16 November 2016 19:49 To: LXC users mailing-list Subject: Re: [lxc-users] What are the options for connecting to storage? What about using a bind-mount? Mount your iscsi volume to the LXD server and bind-mount it into the container. A quick URL: https://github.com/lxc/lxd/issues/2005 On Nov 16, 2016, at 11:42 AM, McDonagh, Ed <ed.mcdon...@rmh.nhs.uk<mailto:ed.mcdon...@rmh.nhs.uk>> wrote: Hi I need to create a container that has access to a couple of TB to store image files (mostly 8MB upwards). My instinct is to create an iSCSI target on my Synology server and connect from the container to get a new disk that I can use for the storage. I understand that the guest has to be privileged to do any sort of connection to storage, however it seems that the iSCSI node in the container doesn’t work. What are my options? Do I need to use a SMB connection to the Synology server? Or is NFS better? Is there a way to connect using iSCSI? If it makes any difference, I have two identical servers that I am running LXD on, and want to be able to move the containers between them for maintenance etc. Ideally live, but not essential. And that doesn’t seem to work anyway with lxd 2.0, so kind of a moot point! Any help, suggestions or advice would be very welcome. Kind regards Ed Ed McDonagh Head of Scientific Computing (Diagnostic Radiology) Joint Department of Physics The Royal Marsden NHS Foundation Trust Tel 020 7808 2512 Fax 020 7808 2522 <image001.jpg> ________________________________ Attention: This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary, confidential and/or privileged information and should not be copied, disclosed, distributed, retained or used by any other party. If you are not an intended recipient please notify the sender immediately and delete this e-mail (including attachments and copies). The statements and opinions expressed in this e-mail are those of the author and do not necessarily reflect those of the Royal Marsden NHS Foundation Trust. The Trust does not take any responsibility for the statements and opinions of the author. Website: http://www.royalmarsden.nhs.uk<http://www.royalmarsden.nhs.uk/> ________________________________ _______________________________________________ lxc-users mailing list lxc-users@lists.linuxcontainers.org<mailto:lxc-users@lists.linuxcontainers.org> http://lists.linuxcontainers.org/listinfo/lxc-users ######################################################################### Attention: This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary, confidential and/or privileged information and should not be copied, disclosed, distributed, retained or used by any other party. If you are not an intended recipient please notify the sender immediately and delete this e-mail (including attachments and copies). The statements and opinions expressed in this e-mail are those of the author and do not necessarily reflect those of the Royal Marsden NHS Foundation Trust. The Trust does not take any responsibility for the statements and opinions of the author. Website: http://www.royalmarsden.nhs.uk #########################################################################
_______________________________________________ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
