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 ourterms of serviceand privacy statement.We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

lstat /host_mnt: function not implemented when using:z #6634

Closed
2 tasks done
billyfossopened this issue May 11, 2020 · 18 comments
Closed
2 tasks done

lstat /host_mnt: function not implemented when using:z #6634

billyfossopened this issue May 11, 2020 · 18 comments

Comments

@billyfoss
Copy link

billyfoss commented May 11, 2020

Upgraded to 2.3.0.2 today and found that mounts are not working as they did before.

  • I have tried with the latest version of my channel (Stable or Edge)
  • I have uploaded Diagnostics
  • Diagnostics ID: B86D9DE7-77D8-4B7E-A1FF-1228340E07E0/20200511214828

Expected behavior

This output was from without:z

$ docker run --rm -it -v C:/tmp:/tmp:z centos:7 /bin/bash
[root@b9a769b285d4 /]# ls -alZ /tmp
drwxrwxrwx root root?.
drwxr-xr-x root root?..

Actual behavior

$ docker run --rm -it -v C:/tmp:/tmp:z centos:7 /bin/bash
docker: Error response from daemon: error evaluating symlinks from mount source "/host_mnt/c/tmp": lstat /host_mnt: function not implemented.

Information

This is happening consistently now. Previously, I had tried Edge and had occasional function not implemented error messages. Restarting Docker resolved the issue before, but this appears to be consistent with the new version of the Stable channel.
I am running within Ubuntu 18.04 using WSL1

  • Windows Version: Windows 10 Pro (1903 - 18362.778)
  • Docker Desktop Version: 2.3.0.2
  • Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM: No

Steps to reproduce the behavior

  1. Install new version
  2. Run with:z
docker run --rm -it -v C:/tmp:/tmp:z centos:7 /bin/bash
@djs55
Copy link

djs55 commented May 12, 2020

Thanks for your report. Could I just check: does it work ok for you without:z?The Linux VM inside Docker Desktop does not enable SELinux so labelling ought not to be necessary.

@Gemorroj
Copy link

link to version 2.2.0.5
https://docs.docker /docker-for-windows/release-notes/#docker-desktop-community-2205

@dquintela
Copy link

dquintela commented May 12, 2020

I have the same issue with the docker for windows update I did yesterday.

C:\data\projects\audit-service\service>docker run -v c:\data\projects\audit-service\service\target\audit-service-1.0.0-SNAPSHOT-native-image-source-jar:/project:z --env LANG=C --rm quay.io/quarkus/ubi-quarkus-native-image:20.0.0-java11 -J-Djava.util.logging.manager=org.j Boss.logmanager.LogManager -J-Dsun.nio.ch.maxUpdateArraySize=100 -J-Dvertx.logger-delegate-factory-class-name=io.quarkus.vertx.core.runtime.VertxLogDelegateFactory -J-Dvertx.disableDnsResolver=true -J-Dio.netty.leakDetection.level=DISABLED -J-Dio.netty.allocator.maxOrder=1 -J-Duser.language=en -J-Dfile.encoding=Cp1252 --initialize-at-build-time= -H:InitialCollectionPolicy=com.oracle.svm.core.genscavenge.CollectionPolicy$BySpaceAndTime -H:+JNI -jar audit-service-1.0.0-SNAPSHOT-runner.jar -H:FallbackThreshold=0 -H:+ReportExceptionStackTraces -H:-AddAllCharsets -H:-IncludeAllTimeZones -H:EnableURLProtocols=http -H:-UseServiceLoaderFeature -H:+StackTrace audit-service-1.0.0-SNAPSHOT-runner
docker: Error response from daemon: error evaluating symlinks from mount source "/host_mnt/c/data/projects/audit-service/service/target/audit-service-1.0.0-SNAPSHOT-native-image-source-jar": lstat /host_mnt: function not implemented.

Removed the ":v" and with works

C:\data\projects\audit-service\service>docker run -v c:\data\projects\audit-service\service\target\audit-service-1.0.0-SNAPSHOT-native-image-source-jar:/project --env LANG=C --rm quay.io/quarkus/ubi-quarkus-native-image:20.0.0-java11 -J-Djava.util.logging.manager=org.j Boss.logmanager.LogManager -J-Dsun.nio.ch.maxUpdateArraySize=100 -J-Dvertx.logger-delegate-factory-class-name=io.quarkus.vertx.core.runtime.VertxLogDelegateFactory -J-Dvertx.disableDnsResolver=true -J-Dio.netty.leakDetection.level=DISABLED -J-Dio.netty.allocator.maxOrder=1 -J-Duser.language=en -J-Dfile.encoding=Cp1252 --initialize-at-build-time= -H:InitialCollectionPolicy=com.oracle.svm.core.genscavenge.CollectionPolicy$BySpaceAndTime -H:+JNI -jar audit-service-1.0.0-SNAPSHOT-runner.jar -H:FallbackThreshold=0 -H:+ReportExceptionStackTraces -H:-AddAllCharsets -H:-IncludeAllTimeZones -H:EnableURLProtocols=http -H:-UseServiceLoaderFeature -H:+StackTrace audit-service-1.0.0-SNAPSHOT-runner
Build on Server(pid: 27, port: 34685)*
[audit-service-1.0.0-SNAPSHOT-runner:27] classlist: 10,487.90 ms, 1.00 GB
[audit-service-1.0.0-SNAPSHOT-runner:27] (cap): 1,042.24 ms, 1.00 GB
[audit-service-1.0.0-SNAPSHOT-runner:27] setup: 3,066.04 ms, 1.00 GB
10:09:09,846 INFO [org.jbo.res.res.i18n] RESTEASY002225: Deploying javax.ws.rs.core.Application: class com...audit.service.resources.AuditInvocationApplication
10:09:31,877 INFO [org.jbo.threads] JBoss Threads version 3.1.1.Final
[audit-service-1.0.0-SNAPSHOT-runner:27] (typeflow): 40,911.71 ms, 1.54 GB
[audit-service-1.0.0-SNAPSHOT-runner:27] (objects): 36,399.59 ms, 1.54 GB
[audit-service-1.0.0-SNAPSHOT-runner:27] (features): 749.38 ms, 1.54 GB
[audit-service-1.0.0-SNAPSHOT-runner:27] analysis: 81,218.45 ms, 1.54 GB
[audit-service-1.0.0-SNAPSHOT-runner:27] (clinit): 1,351.74 ms, 1.54 GB
[audit-service-1.0.0-SNAPSHOT-runner:27] universe: 5,070.65 ms, 1.54 GB
[audit-service-1.0.0-SNAPSHOT-runner:27] (parse): 11,913.59 ms, 1.54 GB
[audit-service-1.0.0-SNAPSHOT-runner:27] (inline): 10,291.82 ms, 1.54 GB
[audit-service-1.0.0-SNAPSHOT-runner:27] (compile): 56,918.56 ms, 1.54 GB
[audit-service-1.0.0-SNAPSHOT-runner:27] compile: 81,995.23 ms, 1.54 GB
[audit-service-1.0.0-SNAPSHOT-runner:27] image: 4,103.80 ms, 1.54 GB
[audit-service-1.0.0-SNAPSHOT-runner:27] write: 3,226.69 ms, 1.54 GB
[audit-service-1.0.0-SNAPSHOT-runner:27] [total]: 189,638.42 ms, 1.54 GB

@Tieantono
Copy link

Tieantono commented May 12, 2020

Not only Z drive I guess, it also happened on my C or D drives.
I've got a similar problem when mounting a volume on the same Docker version2.3.0.2when I want to run adocker-composefile fromhere

Error messages when runningdocker-compose up -dcommand:

ERROR: for docker-jitsi-meet_prosody_1 Cannot start service prosody: error evaluating symlinks from mount source "/host_mnt/d/Jitsi/.jitsi-meet-cfg/prosody/config": lstat /host_mnt: function not implemented

ERROR: for docker-jitsi-meet_web_1 Cannot start service web: error evaluating symlinks from mount source "/host_mnt/d/Jitsi/.jitsi-meet-cfg/transcripts": lstat /host_mnt: function not implemented

ERROR: for prosody Cannot start service prosody: error evaluating symlinks from mount source "/host_mnt/d/Jitsi/.jitsi-meet-cfg/prosody/config": lstat /host_mnt: function not implemented

ERROR: for web Cannot start service web: error evaluating symlinks from mount source "/host_mnt/d/Jitsi/.jitsi-meet-cfg/transcripts": lstat /host_mnt: function not implemented

My Windows specifications:
Windows Version: Windows 10 Pro (1809 - 17763.1158)
Running within Ubuntu 18.04 using WSL1

@dquintela
Copy link

Just downgraded back to Docker Desktop Community 2.2.0.5 and it's working again.
https://docs.docker /docker-for-windows/release-notes/

@Tieantono
Copy link

Tieantono commented May 12, 2020

Just downgraded back to Docker Desktop Community 2.2.0.5 and it's working again.
https://docs.docker /docker-for-windows/release-notes/

Yes, it is working on version 2.2.0.5. Thank you.

@rincler
Copy link

rincler commented May 12, 2020

The same problem on 2.3.0.2

@stephen-turner
Copy link
Contributor

stephen-turner commented May 12, 2020

Thanks for the reports.@thaJeztahtells us that this is due to a known bug in the upstream engine:moby/moby#40944.The flag is supposed to be ignored, but is throwing an error instead. We'll be able to fix it when the fix has made it into an engine patch release.

@yehoshuadimarsky
Copy link

The same problem on 2.3.0.2

same here

@thaJeztah
Copy link
Member

If you're having this issue with the:zor:Zoptions (SELinux labeling), the workaround is to remove that option; even with the issue fixed, those options won't have an effect when using docker desktop (the fix linked above (to be released in the next engine patch release) is to ignore the error of the underlying filesystem doesn't support xattrs / SELinux labels which is the case with docker desktop)

@jackdcasey
Copy link

To anyone running into this issue when using the serverless framework, I was able to get things functional by downgrading to version2.2.0.5.

Hope this prevents a headache for anyone else running into this! 😁

@CaliforniaMountainSnake

I have the same problem.
Cannot start service mysql: error evaluating symlinks from mount source "/host _mnt/d/Servers/www/project/logs/mysql": lstat /host_mnt: function not implemented

@thaJeztah
Copy link
Member

Yes, it is working on version 2.2.0.5. Thank you.

Actually;@stephen-turnerdouble checking w.r.t. the SELinux (:z/:Z); the regression was in Docker 19.03.7 and 19.03.8 (moby/moby#40547). Looking at therelease notes,Docker Desktop 2.2.0.5 already had engine 19.03.8, so if it works with 2.2.0.5, but doesn't work with 2.3.0.x, I think it's a different issue

@valentijnscholten
Copy link

It also fails when using docker-compose, without any:zin mounts specified.

@mat007
Copy link
Member

mat007 commented May 15, 2020

Thanks for the reports, we understand where this is coming from now and are working on a fix!

@robrechta
Copy link

any idea when the fix of this issue is planned? I see a build 2.3.0.3 appearing, but this ticket is still open... So I don't want to loose time of doing an upgrade, and then back a downgrade to 2.2.0.5...

@mat007
Copy link
Member

mat007 commented May 27, 2020

The fix has now been released in Docker Desktop Stable 2.3.0.3, I’ll go ahead and close this issue.

@docker-robott
Copy link
Collaborator

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

@docker docker locked and limited conversation to collaborators Jul 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests