Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix volumes #1

Open
ju55i opened this issue Oct 31, 2014 · 2 comments
Open

Fix volumes #1

ju55i opened this issue Oct 31, 2014 · 2 comments

Comments

@ju55i
Copy link
Owner

ju55i commented Oct 31, 2014

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.

@silvio
Copy link

silvio commented Jun 10, 2015

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?

@ju55i
Copy link
Owner Author

ju55i commented Jun 11, 2015

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants