uxora-com

Sorry for the late reply, and that's great you figured that out by yourself. But it was already written in this Readme here: https://github.com/uxora-com/xpenology-docker

@T-REX-XP It can be found here:

That's nice of you, @RobbieT, to help ppl by copying and paste a part of my tutorial. Of course, u can copy/paste as much as u want to help ppl ... But u know, what is even better and nicer ? It's to specify the source where it comes from https://www.uxora.com/other/virtualization/55-install-xpenology-dsm-6-2-x-on-proxmox#Changexpenologyparameteringrub.cfg .

From this docker, yes because this is how it has been designed. But it is just needed once at the first container's run. If you don't have a webserver, you can use gofile.io as explained in the tutorial. HTH

You got all links in this tutorial : https://www.uxora.com/other/virtualization/57-xpenology-on-docker I'm not sure what you really try to do so the only advise I think i can give you is the less layers you got the better it get: 1- Baremetal -> DSM 2- Baremetal -> OS -> Qemu-kvm -> DSM 3- Baremetal -> OS -> Lxc/Docker -> Qemu-kvm -> DSM 4- Baremetal -> OS -> Lxc -> Docker -> Qemu-kvm -> DSM Qemu-kvm is a VM and it is isolated enough so it doesn't really need to add another jail stuff I think. But it all depends on what you want to do and the capabilities of your first OS layer. HTH

I don't really use 9p in my main xpenology, but just play with it a bit on a test system. 9p allow you to passthrough a folder from host to VM, and yes, I was able to make it as a DSM shared folder. For that, you just need to create the folder as root, then mount it as 9p, then create a shared folder on DSM with with same folder name. For ex: [root]$ mkdir /volume1/datashare [root]$ mount -t 9p -o trans=virtio,version=9p2000.L,msize=262144 hostdata /volume1/datashare/ # And then create "datashare" DSM shared folder in volume1 Maybe this can be done with NFS as well, I have never tried it yet but I don't see why this cannot be done. For encrypted shared folder, I have never tried so I don't know ... let us know if to get this working. HTH

On my test machine, I run docker container as root on a Debian 10. I just tried and it works for me ... I don't have any permission issue and 9p mount is working as well. If it cannot create vdisk on /datashare then the permission issue is between the Host/User->Docker->Container ... and not the virtual machine running inside the container. As I suggest to whuang, try to get terminal access to linux OS container with the following command (when container is running) : docker exec -ti $( docker container ls -f 'ancestor=uxora/xpenology' -f "status=running" -q ) /bin/bash Then try to test/debug/figure out why you have permission issue which can be due to : - Docker configuration issues - Host or User permissions issues And let us know if you find out the issue. HTH

I don't use UNRAID and don't really know how it manages docker. - "most of the time by DSM itself" : DSM can restart (which do not close the container) or it can shutdown (which normally terminate the container at the end) - "either by unraid" : Not sure how it manages docker but if it runs the full docker parameters when it restart, then this will create a new container at every restart. A new container will create new virtual disks if not exists, and need to do dsm installation again. Normally you should run the full run parameter only once to create the container, then you can stop/start/restart the container with the containerID (ie. docker container start <containerID>). Otherwise, if you really want/need to create new container at every reboot (and don't care about saving disk space 😛 ) then "maybe" you can try to change DISK_PATH to a external storage (outside the container) like "/datashare" to store virtual disks. HTH

Hi, How do you restart your docker container?

Adding "-it --entrypoint /bin/bash" makes the containers run "/bin/bash" instead of default "/usr/bin/vm-startup" (define in Dockerfile). This gives you access to the command line in the uxora/xpenology container and it's in there you can find "/usr/bin/vm-startup"! Maybe once you get command line access to the containers, I dont know ... try to find out what the issue by running for exemple: - $ iptables -A POSTROUTING -t mangle -p udp --dport bootpc -j CHECKSUM --checksum-fill - $ /usr/bin/vm-startup If you don't really make an effort to really find out, I cannot be much help. Sorry. HTH == "Hope That helps"

As I did reply to you already in the article, for me, it works on several machine without getting this issue. This error may come from your Docker/Host machine configuration. However, the following command seems to be the one throwing that error: # Hack for guest VMs complaining about "bad udp checksums in 5 packets" $ iptables -A POSTROUTING -t mangle -p udp --dport bootpc -j CHECKSUM --checksum-fill You can try to test/debug by running a bash prompt with "-it --entrypoint /bin/bash" as follow: docker run --privileged --cap-add=NET_ADMIN \ --device=/dev/net/tun --device=/dev/kvm \ -e CPU="qemu64" \ -e THREADS=1 \ -e RAM=512 \ -e DISK_SIZE="8G 10G" \ -e DISK_PATH="/image" \ -e BOOTLOADER_URL="http://192.168.1.10/synoboot_104b_ds918plus_virtio_9p.img" \ -e BOOTLOADER_AS_USB="Y" \ -e VM_ENABLE_VIRTIO="Y" \ -it --entrypoint /bin/bash \ uxora/xpenology Try to test and see why the faulty "iptables" command does not work. Or edit "/usr/bin/vm-startup" script as you please (maybe like removing faulty cmd) Then run that script to launch xpenology kvm. Let me know if you find something... like this I may change the script to be more compatible. HTH

I don't know which bootloader and dsm version you are using ... But I just tried on a new docker with "synoboot_103b_ds3615xs_virtio_9p.img" bootloader and DSM_DS3615xs_25426.pat, and it still work for me by following this tutorial : https://www.uxora.com/other/virtualization/57-xpenology-on-docker

Probably because your URL pointing to bootloader is not valid. And you do not have user permission to modify network configuration (try to run it as root) Check this article which may help you: https://www.uxora.com/other/virtualization/57-xpenology-on-docker HTH

Read "Variables" and "Mount Docker Host Volumes to Xpenology" part of the documentation here: https://hub.docker.com/r/uxora/xpenology In Docker, if you use default value of VM_PATH_9P (Default "/datashare") then you should use docker -v option like "-v /shared/data:/datashare". In xpenology terminal, use :"$ sudo mount -t 9p -o trans=virtio,version=9p2000.L,msize=262144 hostdata /volume1/datashare". HTH

I found these bootloader, with virtio drivers loaded, that may work for you: 😀 - ds3617xs : https://gofile.io/d/pnBQbd It does not work for me, it launch but stay block at "Loading module adt7475", don't know why. But it does work directly as proxmox vm without docker. -ds918+ : https://gofile.io/d/wfNCxt It works for me in mxlinux usb live but it does not works on my proxmox VM or Lxc container. For this bootloader, you need to specify the VM_MAC to docker as follow: -e VM_MAC="00:11:32:12:34:56" You can give it a try if you want, if so ... then let me know how it goes for you.

Thank you for your feedback, can i ask you which hardware and os are you using ? I haven't tried ds3617xs and ds918+ yet ... I will work on it when got some spare time. Ok good, can i ask you which hardware and os are you using as well? Thanks.

For those, who still are interested in running a Xpenology on a Docker ... I have forked and updated this project to make it works with dsm 6.2.3. Here is the link: - to the source project: https://github.com/uxora-com/xpenology-docker - to the docker hub image : https://hub.docker.com/r/uxora/xpenology And last, here is the link to the bootloader with virtio loaded at boot : https://gofile.io/d/bym4Cc Note that "download" url in webpage on this link can be used as BOOTLOADER_URL once it has been generated by clicking on the link. Instruction: - Install Docker - Then run: $ docker run --privileged \ -p 5000:5000 -p 5001:5001 -p 2222:22 -p 8080:80 \ -e RAM=512 \ -e DISK_SIZE="32G" \ -e BOOTLOADER_URL="http://example.com/path/synoboot.img" \ -e BOOTLOADER_AS_USB="Y" \ -e VM_ENABLE_VIRTIO="Y" \ uxora/xpenology Let me know if it works (or not) for you.