ronivay/xen-orchestra-docker

Xen Orchestra in a docker container

xen-orchestra-docker's Issues

The latest image (5.100.1) is not working

I'm running xen-orchestra as a K8s workload. Starting the latest image I get the error below repeatedly in the logs and the page does not load even though the container goes to a running state. Rolling back to the previous image (5.100.0) solves the issue for me. This is repeatable. So something in the latest image breaks at least for my setup.

(node:32) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency
(Use node --trace-warnings ... to show where the warning was created)
[2022-08-10T12:39:47+0000] info : 'rpcbind' start: '/sbin/rpcbind'
[2022-08-10T12:39:48+0000] info : 'rpcbind' start action done
[2022-08-10T12:39:48+0000] info : 'xo-opm-7fffb55b8f-bbt7f' start action done
[2022-08-10T12:39:48+0000] info : Awakened by User defined signal 1
[2022-08-10T12:39:48+0000] info : 'redis' start action done
2022-08-10T12:39:50.600Z xo:main INFO Configuration loaded.
2022-08-10T12:39:50.607Z xo:main INFO Web server listening on http://[::]:80
2022-08-10T12:39:50.637Z xo:main INFO Web server listening on https://[::]:443
2022-08-10T12:39:50.906Z xo:mixins:hooks WARN start failure {
error: Error: spawn xenstore-read ENOENT
at Process.ChildProcess._handle.onexit (node:internal/child_process:283:19)
at onErrorNT (node:internal/child_process:478:16)
at processTicksAndRejections (node:internal/process/task_queues:83:21) {
errno: -2,
code: 'ENOENT',
syscall: 'spawn xenstore-read',
path: 'xenstore-read',
spawnargs: [ 'vm' ],
cmd: 'xenstore-read vm'
}
}

Can't mount nfs remote (In XO / Settings / Remotes )

Hello,

I've tried using the docker image and it failed to mount the nfs remote.

Command failed with exit code 32: mount -o vers=3 -t nfs 192.168.100.7:/volume1/xcp-01-backup /run/xo-server/mounts/d8efc3a5-7b13-4992-88e9-8d3555969255 mount.nfs: access denied by server while mounting 192.168.100.7:/volume1/xcp-01-backup

From the host, the mount works mount -o vers=3 -t nfs 192.168.100.7:/volume1/xcp-01-backup /mnt .
I'm running docker with this command:

docker run -itd --name xo \
     --restart unless-stopped \
     --cap-add sys_admin \
     --stop-timeout 60 \
     -p 80:80 \
     -v /var/lib/xo-server/server-data:/var/lib/xo-server \
     -v /var/lib/xo-server/redis-data:/var/lib/redis \
      ronivay/xen-orchestra

The VM has two network interfaces.
I'm running debian 10.5.

uname -a
Linux xo 4.19.0-10-amd64 #1 SMP Debian 4.19.132-1 (2020-07-24) x86_64 GNU/Linux

docker --version
Docker version 19.03.13, build 4484c46d9d

File Restore Not Working

I am running XenOrchestra Docker Container on a Synology NAS. I am running it will Full Permissions and everything seems to work great except one thing, it won't do the File Restore. Backups and VM Restore works good. For File Restore, I can get to picking the partitions, but then doesn't show the files/folders in the partitions. The backups are on NFS Partitions which are hosted on the parent Synology NFS File Shares and that connection seems to be fine. I am wondering if there is some package missing to get files to extract out of the images?

Hardware:

• Synology 1621+
• AMD Ryzen V1500B processor
• 32GB RAM, 4 Cores

arm64 build failing

I noticed the last 3 workflows have failed, and my container now hasn't updated in nearly a month. Can you take a look?

Unable to change the 80 port

Hi,
/var/lib/xo-server doesn't contain config.toml

Is it possible to change the 80 port somehow?

also passing other from root PGID doesn't make any effect,
drwxr-xr-x 4 root root 4 Jun 11 22:55 data

invalid credentials

Hello,

I had a docker-compose file locally running which worked, but recently I retried on my windows machine and the image boots, I can see the login, but the default credentials consistently just register 'invalid credentials' is there something I am missing?

Is this possibly related to this?
ronivay/XenOrchestraInstallerUpdater#133

filelevel restore with XFS and LVM

Hello,

I try to restore file using file level restore.

My VM has an XFS filesystem over LVM.

Here is the log of the Xen-orchestra container:

xen-orchestra  | 2024-03-03T15:28:56.873Z xo:api WARN [email protected] | backupNg.listFiles(...) [38ms] =!> Error: Command failed: vgchange -ay rl
xen-orchestra  | File descriptor 19 (/var/lib/xo-server/data/leveldb/LOG) leaked on vgchange invocation. Parent PID 54: /usr/local/bin/node
xen-orchestra  | File descriptor 22 (/var/lib/xo-server/data/leveldb/LOCK) leaked on vgchange invocation. Parent PID 54: /usr/local/bin/node
xen-orchestra  | File descriptor 25 (/dev/fuse) leaked on vgchange invocation. Parent PID 54: /usr/local/bin/node
xen-orchestra  | File descriptor 26 (/var/lib/xo-server/data/leveldb/000049.log) leaked on vgchange invocation. Parent PID 54: /usr/local/bin/node
xen-orchestra  | File descriptor 29 (/var/lib/xo-server/data/leveldb/MANIFEST-000047) leaked on vgchange invocation. Parent PID 54: /usr/local/bin/node
xen-orchestra  | File descriptor 112 (/dev/urandom) leaked on vgchange invocation. Parent PID 54: /usr/local/bin/node
xen-orchestra  |   WARNING: VG name rl is used by VGs s12ubK-c4u7-T0Vx-1gnd-WRmN-AHRg-SGOI7F and CyQDuF-5Lk1-cCA3-c0Tb-hd3f-qPl6-JAbFfk.
xen-orchestra  |   Fix duplicate VG names with vgrename uuid, a device filter, or system IDs.
xen-orchestra  |   Multiple VGs found with the same name: skipping rl
xen-orchestra  |   Use --select vg_uuid=<uuid> in place of the VG name.

Do you know why I have theses errors ?

Best regards

ssl connection to XCP-NG using an internal/custom CA certificate

I have setup XCP-NG and XO using custom certificates. I can access both Web UIs just fine using HTTPS.

However, I can't add the XCP-NG host as a server in XO using https. It always show this error

"self signed certificate in certificate chain"

Reading the XO documentation and github link below I see 2 things which are recommended to be set:
https://xen-orchestra.com/docs/configuration.html#link-to-xo-web
vatesfr/xen-orchestra#2659

1. Add the custom CA to /etc/ssl/certs in XO
2. Add "Environment=NODE_OPTIONS=--use-openssl-ca" in /etc/systemd/system/xo-server.service

I can see these are applicable with XO installed from the sources and running in a VM or bare metal.

Is there a way this can be applied using this docker image? Or is there a way I can add a xen server via https using custom CAs.

Cannot start container as of today

Error received:

  error: Script restart attempt #42

  2020-12-12T06:39:10.801Z xo:xo-server ERROR uncaught exception {

  error: Error: /lib64/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by /etc/xen-orchestra/node_modules/argon2/lib/binding/napi-v3/argon2.node)

        at Object.Module._extensions..node (internal/modules/cjs/loader.js:1057:18)

        at Module.load (internal/modules/cjs/loader.js:863:32)

        at Function.Module._load (internal/modules/cjs/loader.js:708:14)

        at Module.require (internal/modules/cjs/loader.js:887:19)

        at require (internal/modules/cjs/helpers.js:74:18)

        at Object.<anonymous> (/etc/xen-orchestra/node_modules/argon2/argon2.js:9:56)

        at Module._compile (internal/modules/cjs/loader.js:999:30)

        at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)

        at Module.load (internal/modules/cjs/loader.js:863:32)

        at Function.Module._load (internal/modules/cjs/loader.js:708:14)

        at Module.require (internal/modules/cjs/loader.js:887:19)

        at require (internal/modules/cjs/helpers.js:74:18)

        at Object.<anonymous> (/etc/xen-orchestra/node_modules/hashy/index.js:124:4)

        at Module._compile (internal/modules/cjs/loader.js:999:30)

        at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)

        at Module.load (internal/modules/cjs/loader.js:863:32)

        at Function.Module._load (internal/modules/cjs/loader.js:708:14)

        at Module.require (internal/modules/cjs/loader.js:887:19)

        at require (internal/modules/cjs/helpers.js:74:18)

        at Object.<anonymous> (/etc/xen-orchestra/packages/xo-server/src/xo-mixins/subjects.js:4:1)

        at Module._compile (internal/modules/cjs/loader.js:999:30)

        at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)

        }

  error: Forever detected script exited with code: 0

Container does not start

I'm trying to start container but I get an error.

Docker command:
docker run -itd --stop-timeout 60 --restart unless-stopped --cap-add sys_admin --security-opt apparmor:unconfined -p 60080:80 -v /docker-disks/xoa/xo-server:/var/lib/xo-server -v /docker-disks/xoa/redis:/var/lib/redis ronivay/xen-orchestra

Container log:

New Monit id: 9f3a501735583ce69af91ec19663fcc0
 Stored in '/var/lib/monit/id'
[2022-04-23T10:44:15+0000] info     :  New Monit id: 9f3a501735583ce69af91ec19663fcc0
 Stored in '/var/lib/monit/id'
Starting Monit 5.27.1 daemon with http interface at [localhost]:2812
[2022-04-23T10:44:15+0000] info     : Starting Monit 5.27.1 daemon with http interface at [localhost]:2812
[2022-04-23T10:44:15+0000] info     : '81ead8ceb795' Monit 5.27.1 started
[2022-04-23T10:44:15+0000] error    : 'redis' process is not running
[2022-04-23T10:44:15+0000] info     : 'redis' trying to restart
[2022-04-23T10:44:15+0000] info     : 'redis' start: '/usr/bin/redis-server /etc/redis/redis.conf --bind 127.0.0.1 --pidfile /var/run/redis.pid'
[2022-04-23T10:44:15+0000] info     : 'xo-server' start on user request
[2022-04-23T10:44:15+0000] info     : '81ead8ceb795' start on user request
[2022-04-23T10:44:15+0000] info     : 'rpcbind' start on user request
[2022-04-23T10:44:15+0000] info     : 'redis' start on user request
[2022-04-23T10:44:15+0000] info     : Monit daemon with PID 13 awakened
15:C 23 Apr 2022 10:44:15.289 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
15:C 23 Apr 2022 10:44:15.289 # Redis version=5.0.14, bits=64, commit=00000000, modified=0, pid=15, just started
15:C 23 Apr 2022 10:44:15.289 # Configuration loaded
                _._                                                  
           _.-``__ ''-._                                             
      _.-``    `.  `_.  ''-._           Redis 5.0.14 (00000000/0) 64 bit
  .-`` .-```.  ```\/    _.,_ ''-._                                   
 (    '      ,       .-`  | `,    )     Running in standalone mode
 |`-._`-...-` __...-.``-._|'` _.-'|     Port: 6379
 |    `-._   `._    /     _.-'    |     PID: 18
  `-._    `-._  `-./  _.-'    _.-'                                   
 |`-._`-._    `-.__.-'    _.-'_.-'|                                  
 |    `-._`-._        _.-'_.-'    |           http://redis.io        
  `-._    `-._`-.__.-'_.-'    _.-'                                   
 |`-._`-._    `-.__.-'    _.-'_.-'|                                  
 |    `-._`-._        _.-'_.-'    |                                  
  `-._    `-._`-.__.-'_.-'    _.-'                                   
      `-._    `-.__.-'    _.-'                                       
          `-._        _.-'                                           
              `-.__.-'                                               

18:M 23 Apr 2022 10:44:15.290 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
18:M 23 Apr 2022 10:44:15.290 # Server initialized
18:M 23 Apr 2022 10:44:15.290 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
18:M 23 Apr 2022 10:44:15.290 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
18:M 23 Apr 2022 10:44:15.290 * Ready to accept connections
[2022-04-23T10:44:15+0000] info     : 'redis' process is running with pid 18
[2022-04-23T10:44:15+0000] info     : 'xo-server' start: '/usr/local/bin/forever start -a --pidFile /var/run/xo-server.pid --sourceDir /etc/xen-orchestra/packages/xo-server -l /var/log/xo-server.log dist/cli.mjs'
(node:33) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
internal/modules/cjs/loader.js:902
  const err = new Error(message);
              ^

Error: Cannot find module 'assert/strict'
Require stack:
- /etc/xen-orchestra/@vates/cached-dns.lookup/index.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
    at Function.Module._load (internal/modules/cjs/loader.js:746:27)
    at Module.require (internal/modules/cjs/loader.js:974:19)
    at require (internal/modules/cjs/helpers.js:101:18)
    at Object.<anonymous> (/etc/xen-orchestra/@vates/cached-dns.lookup/index.js:3:16)
    at Module._compile (internal/modules/cjs/loader.js:1085:14)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
    at Module.load (internal/modules/cjs/loader.js:950:32)
    at Function.Module._load (internal/modules/cjs/loader.js:790:12)
    at ModuleWrap.<anonymous> (internal/modules/esm/translators.js:199:29)
    at ModuleJob.run (internal/modules/esm/module_job.js:183:25)
    at async Loader.import (internal/modules/esm/loader.js:178:24)
    at async Object.loadESM (internal/process/esm_loader.js:68:5)
    at async handleMainPromise (internal/modules/run_main.js:59:12) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ '/etc/xen-orchestra/@vates/cached-dns.lookup/index.js' ]
}
{"level":"error","message":"Forever detected script exited with code: 1"}

I did something wrong?

No vm or host stats

VM & host stats show "no stats". I also see the following in the logs:

"2020-05-24T13:49:14.276Z xo:api WARN sgordon | vm.stats(...) [21s] =!> FaultyGranularity: Unable to get the true granularity: 60 "

NTFS support?

HOST TrueNAS-SCALE-22.02.4
Docker XO commit b63c4
xo-server 5.104.0
xo-web 5.105.0

Issue
Trying to restore file from NTFS partition.

Installation logfile
xo:api WARN admin | backupNg.listFiles(...) [213ms] =!> Error: Command failed: mount --options=loop,ro,norecovery,sizelimit=71571603456,offset=368050176 --source=/tmp/qfs18qcazn/vhd0 --target=/tmp/u1jfb36ljvk
mount: /tmp/u1jfb36ljvk: unknown filesystem type 'ntfs'.

---

HOST UNRAID Version: 6.9.2
Docker XO commit 31f85 (tag 5.109.0)
xo-server 5.109.0
xo-web 5.111.0

Issue
Trying to restore file from NTFS partition.

Installation logfile
xo:api WARN admin | backupNg.listFiles(...) [367ms] =!> Error: Command failed: mount --options=loop,ro,norecovery,sizelimit=71571603456,offset=368050176 --source=/tmp/fk9v3yqexdp/vhd0 --target=/tmp/i32r5s4zroc
mount: /tmp/i32r5s4zroc: wrong fs type, bad option, bad superblock on /dev/loop4, missing codepage or helper program, or other error.

---

I'm certain that in some of previous version it was working.

PS: Sorry for wrong repository.

issue with remotes

Hi

I am having an issue with backup remotes and I have reached out to xcp directly
vatesfr/xen-orchestra#6818

Just wanted to make you aware in case the issue is on your side.

The only thing that stood out was to ensure cifs-utils is installed on the container.
From this post
https://xcp-ng.org/forum/topic/2169/backups-to-smb-remote-failing/12

Please let me know if you have any insights.

docker pull ronivay/xen-orchestra-docker

Wrong registry name i readme.

docker pull ronivay/xen-orchestra-docker -> docker pull ronivay/xen-orchestra

Build didn't run due to repo inactivity.

I use this and watchtower to auto-update XO weekly. Saw my container didn't update last night.

Looked at https://github.com/ronivay/xen-orchestra-docker/actions/workflows/build.yml and saw "This scheduled workflow is disabled because there hasn't been activity in this repository for at least 60 days. Enable this workflow to resume scheduled runs."

Custom cert definition, script error

When I define variable HTTPS_PORT, CERT_PATH and KEY_PATH then error occur.

Environment variables:
HTTPS_PORT=443
CERT_PATH='/cert.pem'
KEY_PATH='/cert.key'

Volumes definition:
-v /mnt/user/appdata/XO/certs/cert.pem:/cert.pem
-v /mnt/user/appdata/XO/certs/cert.key:/cert.key \

Files are accessible within the container.

LOG:
`✖ Unexpected character, expecting string, number, datetime, boolean, inline array or inline table at row 102, col 8, pos 2770:
101: autoCert = true
102> cert = /cert.pem

         ^

103: key = /cert.key
TomlError: Unexpected character, expecting string, number, datetime, boolean, inline array or inline table at row 102, col 8, pos 2770:
101: autoCert = true
102> cert = /cert.pem

         ^

103: key = /cert.key`

It is pointing to the slash.

Request: Latest-official tag

I noticed that with the tags, there are 2 choices:

1. latest: uses the nightlies
2. specific version

Would it be possible to create a new tag of "latest-official" (or something else) that doesn't use the nightlies, but would upgrade official incremental releases (i.e. 5.47 to 5.48 when officially released).

Full backup of VM is failing after 5.100.1

If I launch XOA with version 5.100.1, VM backup on an a NFS remote is working fine. This is how the log looks like.

Snapshot
Start: Oct 29, 2022, 03:03:01 AM
End: Oct 29, 2022, 03:03:06 AM
Backups on xxxxx
transfer
Start: Oct 29, 2022, 03:03:06 AM
End: Oct 29, 2022, 04:49:28 AM
Duration: 2 hours
Size: 202.62 GiB
Speed: 32.51 MiB/s
Start: Oct 29, 2022, 03:03:06 AM
End: Oct 29, 2022, 04:49:28 AM
Duration: 2 hours
Start: Oct 29, 2022, 03:03:01 AM
End: Oct 29, 2022, 04:49:40 AM
Duration: 2 hours
Type: full

Launching XOA with any versions after 5.100.1, the same back fails. This is how the log looks like:

Snapshot
Start: Oct 30, 2022, 01:55:33 AM
End: Oct 30, 2022, 01:55:38 AM
Backups on xxxxxx
transfer
Start: Oct 30, 2022, 01:55:38 AM
End: Oct 30, 2022, 03:44:08 AM
Duration: 2 hours
Size: 202.62 GiB
Speed: 31.87 MiB/s
Start: Oct 30, 2022, 01:55:38 AM
End: Oct 30, 2022, 03:44:08 AM
Duration: 2 hours
health check
transfer
Start: Oct 30, 2022, 03:44:31 AM
End: Oct 30, 2022, 05:51:59 AM
Duration: 2 hours
Size: 202.62 GiB
Speed: 27.13 MiB/s
vmstart
Start: Oct 30, 2022, 05:51:59 AM
End: Oct 30, 2022, 06:01:59 AM
Error: waitObjectState: timeout reached before OpaqueRef:17c08a88-d669-4090-b2ba-c7ef45909f0b in expected state
Start: Oct 30, 2022, 03:44:26 AM
End: Oct 30, 2022, 06:02:11 AM
Error: waitObjectState: timeout reached before OpaqueRef:17c08a88-d669-4090-b2ba-c7ef45909f0b in expected state
Start: Oct 30, 2022, 01:55:33 AM
End: Oct 30, 2022, 06:02:11 AM
Duration: 4 hours
Error: waitObjectState: timeout reached before OpaqueRef:17c08a88-d669-4090-b2ba-c7ef45909f0b in expected state
Type: full

Looks like XOA after 5.100.1 is doing an extra steps which is making the backup takes longer causing the failure. Any idea what ha changed in the backup after 5.100.1 that is failing on my setup?

docker build 5.132.0 with issues

Hi,
I do really appreciate your work and so I was updating (on a staging system of course) to your latest build 5.132.0.
But It has issues. CPU keep at about 100%. The log produces contineously the following errors:

I stick to 5.131.0 - so there is no issue for my environment. But maybe you want to fix it.

Thanks a lot for providing a easy-to-use CE version of Xen Orchestra to the community!

Best regards, Ralph.

Is it necessary to register with XOA in the cloud to use this container?

This is obviously a XO nood question, but it would strike probably everyone who is new to XO. Maybe this could be answered in the github project info text to avoid the following confusion:

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.

Issue with Google oAuth and container version 5.120.2

The previous container, version 5.119.0 handles Google oAuth fine. When I upgraded to version 5.120.0, I now get this error message: Cannot read properties of undefined (reading 'id').

Now I can downgrade to 5.119.0, but I'd like to know what the above error message means. I double checked the Google Authentication module's settings and everything was set as it should be.

Any ideas?

Unraid Docker template

Hello,
I've created a template for easy creation of this container in Unraid. I would just like to ask if this is okay with you.
Max