Overview: Support for Docker image XenOrchestra in the sysco repo.

Application: https://xen-orchestra.com

Docker Hub: https://hub.docker.com/r/ronivay/xen-orchestra

GitHub: https://github.com/ronivay/xen-orchestra-docker

Documentation: https://xen-orchestra.com/docs/

reserved for future

Thanks for creating this docker! Been waiting on it for a while.

 

Anyway Im trying to get the SMB remotes to work for backups on the same unraid server but cant seem to get it right. Im running the docker on a custom network at a static IP. I see in the notes to give the docker "Privileged" rights but when I do that all I get is a white screen that says "cannot get /". When I uncheck "Privileged" I can get back to the GUI.

 

Also, when I check "Host access to custom networks" under the unraid docker settings I am able to successfully connect to the SMB share (according to Xen) but as soon as I run a backup I get the error "status_access_denied (0xc0000022) : {access denied} a process has requested access to an object but has not been granted those access rights."

I tried running the docker as a bridge network and changing the http port to 82 (Since unraid uses 80) but the port did not seem to change. I wasnt able to get tp the GUI.

Any idea of what I may be doing wrong to get the SMB backups to work with local unraid storage?

This is obviously a XO noob question, but it would strike probably everyone who is new to XO:

When starting the container and opening the web UI there is a red questions mark in the XOA menu section. also other sections as Hub and XOSAN say "Try XOA for free and deploy it here".

My current (and possible incomplete or wrong) understanding is that this container is an instance of XOA. So what would happen if I went through the procedure to deploy XOA through the containers XO web UI? would this overwrite parts of the container? Is this encouraged or discouraged?

Also if one would run through "deploy XOA", would the Updates button then be usable and do the "right thing"? Or is it discouraged to use Update in the Web UI and rather pull a new version of the container?

As there is no information on these in the container description, I am unsure how to proceed here, as I do not wish to cripple the container accidently by deploying XOA and using Update.