darkl0rd

All containers have a bind mount from the host (which has the EFS filesystem mounted), which looks like: ``` ... volumes: - /host/logs:/logs:ro ... ``` I added promtail 2 days...

Not re-exported, the EFS mount from the host is mapped into the container (a bind mount). (re-)exporting (NFS terminology) would imply that the host exports the filesystem again - it...

There's no indication that it's actually being remounted. An explicit remount (mount -o remount .. ) does also not trigger the behavior. The only pointer at this point is the...

Just to let you know, that this issue didn't go stale ;-), I have just built and deployed HEAD. Will report back in 24h. The log message, do I need...

Sadly no additional logging, output is the same as before: ``` ... I0509 19:11:19.868818 13 filestream.go:131] read /logs/app.log: stale NFS file handle I0509 19:11:19.869217 13 filestream.go:131] read /logs/app.log: stale NFS...

Any idea when this functionality is going to be added? In the interim, is there a way to manually add these to the JMX exporter?

@karolmajek Karol, I will be more than happy to share my experience with Docker Swarm. I have several clusters running and am currently investigating amongst others MooseFS and how well...

Another issue with the "plugin" which is pretty much a showstopper: When you create a volume (docker volume create -d moosefs --name myvolume -o mountpoint=/mnt/moosefs) is that the mountpoint itself...

The problem seems to come forth out of the fact that AWS has decided to name their devices differently. On the instance they are named '/dev/xvdf', whereas in the OS...

First of apologies for opening a new issue, I missed this one. I have an ATSx500 system myself, these systems need to do their initial authentication through a cloud server...