Martin Tarjányi created JCLOUDS-1453:
Summary: Unable to get list of extended attributes - blob store
listing not works with Docker for Windows
Key: JCLOUDS-1453
URL: https://issues.apache.org/jira/browse/JCLOUDS-1453
Project: jclouds
Issue Type: Bug
Components: jclouds-blobstore
Affects Versions: 2.1.1
Reporter: Martin Tarjányi
Environment: Windows 10 Docker
Similar to this bug: https://issues.apache.org/jira/browse/JCLOUDS-1218
When trying to list objects in [S3
proxy|https://github.com/gaul/s3proxy/blob/master/src/main/java/org/gaul/s3proxy/S3ProxyHandler.java#L1322],
jcloud throws the following exception.
Stack trace:
{noformat}
java.nio.file.FileSystemException:
/data/offerservice-pricing-engine-test/intake/high: Unable to get list of
extended attributes: Not supported
at
sun.nio.fs.LinuxUserDefinedFileAttributeView.list(LinuxUserDefinedFileAttributeView.java:119)
at
org.jclouds.filesystem.strategy.internal.FilesystemStorageStrategyImpl.buildPathAndChecksIfBlobExists(FilesystemStorageStrategyImpl.java:712)
at
org.jclouds.filesystem.strategy.internal.FilesystemStorageStrategyImpl.blobExists(FilesystemStorageStrategyImpl.java:293)
at
org.jclouds.blobstore.config.LocalBlobStore$1.apply(LocalBlobStore.java:248)
at
org.jclouds.blobstore.config.LocalBlobStore$1.apply(LocalBlobStore.java:244)
at com.google.common.collect.Iterators$7.computeNext(Iterators.java:652)
at
com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143)
at
com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138)
at
com.google.common.collect.TransformedIterator.hasNext(TransformedIterator.java:43)
at com.google.common.collect.Iterators$7.computeNext(Iterators.java:650)
at
com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143)
at
com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138)
at com.google.common.collect.Iterators.addAll(Iterators.java:361)
at com.google.common.collect.Iterables.addAll(Iterables.java:354)
at com.google.common.collect.Sets.newTreeSet(Sets.java:365)
at
org.jclouds.blobstore.config.LocalBlobStore.list(LocalBlobStore.java:251)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:37)
at com.sun.proxy.$Proxy40.list(Unknown Source)
at
org.gaul.s3proxy.S3ProxyHandler.handleBlobList(S3ProxyHandler.java:1322)
at org.gaul.s3proxy.S3ProxyHandler.doHandle(S3ProxyHandler.java:659)
{noformat}
What I understood from previous bug that the filesystem is not recognized
properly when using docker and JCloud attempts to use XATTR.
Could you give some help how this could be fixed, please?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
