Cesar Talledo

Hi @matthewparkinsondes, Thanks for reporting the problems. Regarding the first problem: > specifying a Data Root of `/data/sysbox` creates the standard 5x directories under both `/var/lib/sysbox` and `/data/sysbox`. I don't...

Regarding: > using systemctl start sysbox ignores config changes in /lib/systemd/system/sysbox.service I don't see this either. For example, this sequence works without problem: 1) Start Sysbox with its default data-root...

Regarding: > specifying a Data Root which is a symlink produces the following error when a System container is launched Given that sysbox-mgr has the `--data-root` option to configure the...

Hi @matthewparkinsondes , > We have been configuring the Data Root by removing --version from the first file and adding --data-root /data/sysbox. Oh I see, that explains your observations; the...

Regarding: > This looks to be a regression in the latest version. Could be, but I don't think it's something we meant to formally support in Sysbox 0.3.0 either. I...

Also: apart from the sysbox-mgr's `--data-root` option, note that sysbox-fs also sets up a FUSE mountpoint which by default is located at `/var/lib/sysboxfs`. This can also be changed via the...

> Apologies for the confusion. We have documentation about this in the Sysbox User Guide's configuration chapter, though I can see further clarification is needed in that doc. I will...

Hi @fhaefemeier, thanks for finding Sysbox and giving it a shot. Your timing is really good, we are just a few days away from the Sysbox v0.5.0 release which includes...

Hi @fhaefemeier, > You mean, it is already functional in the latest code available? Yes that's right. > Do I have to do something special or will it be enough...

Thanks @fhaefemeier. > Only data-root is changed to /srv/container/sysbox instead of /var/lib/sysbox Could you please try with the default data-root (i.e., `/var/lib/sysbox`)? It should work either way, but I wonder...