Xpenology runing on docker


Recommended Posts

  • 3 weeks later...
  • 2 weeks later...

I would like to run this docker on QNAP-4.5.2.1594 but receive errors:

 

[admin@NAS4]# uname -a
Linux NAS4 4.14.24-qnap #1 SMP Tue Mar 2 05:26:12 CST 2021 x86_64 GNU/Linux
[admin@NAS4]# iptables --version
iptables v1.4.21

Maybe the iptables is too old ?

 

INFO: Start downloading bootloader from URL ...

     0K ........ ........ ........ ........ 64% 93.3M 0s
 32768K ........ ........ ..               100% 61.4M=0.6s
INFO: Bootloader has been successfully downloaded from URL.
INFO: /image/bootloader.raw file size seems valid for synoboot.
INFO: Bootloader has been converted to qcow2
INFO: No Initial Disk found, creating disk /image/vm-disk-1.qcow2
Formatting '/image/vm-disk-1.qcow2', fmt=qcow2 size=8589934592 encryption=off cluster_size=65536 lazy_refcounts=off refcount_bits=16
INFO: No Initial Disk found, creating disk /image/vm-disk-2.qcow2
Formatting '/image/vm-disk-2.qcow2', fmt=qcow2 size=17179869184 encryption=off cluster_size=65536 lazy_refcounts=off refcount_bits=16
INFO: KVM acceleration enabled
INFO: Configuring network ...
net.ipv4.ip_forward = 1
INFO: DHCP configured to serve IP 20.20.20.21/24 via dockerbridge
iptables: No chain/target/match by that name.


 

docker run --privileged --cap-add=NET_ADMIN \ --device=/dev/net/tun --device=/dev/kvm \ -p 5007:5000 -p 5008:5001 -p 2222:22 -p 8888:80 \ -e CPU="qemu64" \ -e THREADS=1 \ -e RAM=512 \ -e DISK_SIZE="8G 16G" \ -e DISK_PATH="/image" \ -e BOOTLOADER_URL="http://localhost/synoboot_103b_ds3615xs_virtio_9p.img" \ -e BOOTLOADER_AS_USB="Y" \ -e VM_ENABLE_VIRTIO="Y" \ -v /tmp/tmp:/datashare \ uxora/xpenology

 

Link to post
Share on other sites
Posted (edited)
16 hours ago, s2k7 said:

I would like to run this docker on QNAP-4.5.2.1594 but receive errors:

 

[admin@NAS4]# uname -a
Linux NAS4 4.14.24-qnap #1 SMP Tue Mar 2 05:26:12 CST 2021 x86_64 GNU/Linux
[admin@NAS4]# iptables --version
iptables v1.4.21

Maybe the iptables is too old ?

 



INFO: Start downloading bootloader from URL ...

     0K ........ ........ ........ ........ 64% 93.3M 0s
 32768K ........ ........ ..               100% 61.4M=0.6s
INFO: Bootloader has been successfully downloaded from URL.
INFO: /image/bootloader.raw file size seems valid for synoboot.
INFO: Bootloader has been converted to qcow2
INFO: No Initial Disk found, creating disk /image/vm-disk-1.qcow2
Formatting '/image/vm-disk-1.qcow2', fmt=qcow2 size=8589934592 encryption=off cluster_size=65536 lazy_refcounts=off refcount_bits=16
INFO: No Initial Disk found, creating disk /image/vm-disk-2.qcow2
Formatting '/image/vm-disk-2.qcow2', fmt=qcow2 size=17179869184 encryption=off cluster_size=65536 lazy_refcounts=off refcount_bits=16
INFO: KVM acceleration enabled
INFO: Configuring network ...
net.ipv4.ip_forward = 1
INFO: DHCP configured to serve IP 20.20.20.21/24 via dockerbridge
iptables: No chain/target/match by that name.


 



docker run --privileged --cap-add=NET_ADMIN \ --device=/dev/net/tun --device=/dev/kvm \ -p 5007:5000 -p 5008:5001 -p 2222:22 -p 8888:80 \ -e CPU="qemu64" \ -e THREADS=1 \ -e RAM=512 \ -e DISK_SIZE="8G 16G" \ -e DISK_PATH="/image" \ -e BOOTLOADER_URL="http://localhost/synoboot_103b_ds3615xs_virtio_9p.img" \ -e BOOTLOADER_AS_USB="Y" \ -e VM_ENABLE_VIRTIO="Y" \ -v /tmp/tmp:/datashare \ uxora/xpenology

 

 

 

As suggested by uxora  in the previous post, after deleting following line, the docker started now.

Thanks a lot!

I installed DS3615xs to play.

DS918 seemed failure.

 

# iptables -A POSTROUTING -t mangle -p udp --dport bootpc -j CHECKSUM --checksum-fill

Edited by s2k7
Link to post
Share on other sites
Posted (edited)
4 hours ago, s2k7 said:

 

As suggested by uxora  in the previous post, after deleting following line, the docker started now.

Thanks a lot!

I installed DS3615xs to play.

DS918 seemed failure.

 

# iptables -A POSTROUTING -t mangle -p udp --dport bootpc -j CHECKSUM --checksum-fill

 

I cannot use 9p driver.

Any comments welcome!

 

admin@DS3615:~$ sudo mount -t 9p -o trans=virtio,version=9p2000.L,msize=262144 datashare /volume1/datashare
mount: special device datashare does not exist

 

I passed following settings to docker

    -e VM_PATH_9P="datashare" \
    -v /tmp/tmp:/datashare \

 

Edited by s2k7
Link to post
Share on other sites
  • 2 weeks later...
On 5/30/2021 at 2:32 PM, s2k7 said:

 

I cannot use 9p driver.

Any comments welcome!

 





admin@DS3615:~$ sudo mount -t 9p -o trans=virtio,version=9p2000.L,msize=262144 datashare /volume1/datashare
mount: special device datashare does not exist

 

I passed following settings to docker





    -e VM_PATH_9P="datashare" \
    -v /tmp/tmp:/datashare \

 

 

I figured out.

I have to use "hostdata" which is hard-coded in /usr/bin/vm-startup

"rw" is OK here. I use same uid bwteen host and xpenlogy for convenience.

 

admin@DS3615:~$ sudo mount -t 9p -o trans=virtio,version=9p2000.L,msize=262144 hostdata /volume1/datashare

 

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.