uxora-com

Transition Members
  • Content Count

    18
  • Joined

  • Last visited

Community Reputation

2 Neutral

About uxora-com

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Add a "serial Port (serial0) : socket" to your proxmox vm. Then when your vm is running, you will be able to connect to it from your proxmox server terminal with this following command : $ qm terminal <vmID> HTH
  2. 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
  3. @T-REX-XP It can be found here:
  4. 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 .
  5. 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
  6. 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
  7. 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 w
  8. 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 ) /
  9. 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 sto
  10. Hi, How do you restart your docker container?
  11. 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
  12. 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 --dev
  13. 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
  14. 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
  15. 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