You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Volumes are still kind of a mess. Data should be kept at the host side and mounted at the runtime to the zeo container. I'm getting a OSError: [Errno 16] Device or resource busy: when bringing up the zeo container. I still haven't find out why.
The text was updated successfully, but these errors were encountered:
Because /buildout/var/blobstorage and /buildout/var/filestorage are mounted filesystems.
zope@ff08120c304b:~$ mount
[...]
tmpfs on /buildout/var type tmpfs (rw,nosuid,nodev,relatime)
/dev/sda1 on /buildout/var/blobstorage type btrfs (rw,relatime,nospace_cache)
/dev/sda1 on /buildout/var/filestorage type btrfs (rw,relatime,nospace_cache)
Have you found a solution for this - or you use another plone approach?
I'm thinking of moving the ZODB to a different server altogether. The hosts running Docker should be as stateless as possible and stuff that requires persistence should run separately (with replication if possible). I'm not sure how blobs are going to work with ZEO protocol. Should they be mounted with NFS instead?
Volumes are still kind of a mess. Data should be kept at the host side and mounted at the runtime to the zeo container. I'm getting a OSError: [Errno 16] Device or resource busy: when bringing up the zeo container. I still haven't find out why.
The text was updated successfully, but these errors were encountered: