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
===========================================================
With the following lines in daemonset.yaml
/var is mounted with s3 (i.e. changes made in s3 is reflected in /var folder in container and vice versa)
/var:shared is mounted with /mnt/s3data (i.e changes made in /var:shared folder in container is reflected in host and vv)
However /var , /var:shared and s3 bucket is not in sync.
Probably mount Propagation is not working as expected.
Kindly suggest in case of any suggestion or possible workarounds/solutions.
The text was updated successfully, but these errors were encountered:
You should try making a mount point in /var (the directory that will map to the host directory /mnt/s3data) without using :shared. In the command section, first generate the directory where the s3 bucket will be mounted, which must be inside /var (e.g /var/bucket) because when the daemonset makes the mount point /var it overlaps the content from /var folder inside the container . In the section volumeMounts you need to add mountPropagation: Bidirectional to convey with Mount Propagation by Kubernetes
So I think if you can translate it to your scenario, maybe it will work for you.
===========================================================
With the following lines in daemonset.yaml
/var is mounted with s3 (i.e. changes made in s3 is reflected in /var folder in container and vice versa)
/var:shared is mounted with /mnt/s3data (i.e changes made in /var:shared folder in container is reflected in host and vv)
However /var , /var:shared and s3 bucket is not in sync.
Probably mount Propagation is not working as expected.
Kindly suggest in case of any suggestion or possible workarounds/solutions.
The text was updated successfully, but these errors were encountered: