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

:cached volume and case-insensitive filename #2096

Closed
Nondv opened this Issue Sep 28, 2017 · 9 comments

Comments

Projects
None yet
4 participants
@Nondv
Copy link

Nondv commented Sep 28, 2017

Hello!
I have a bug to report.

I mount my project to container via docker-compose (but I guess it's not compose related):

volumes:
  -'.:/project:cached'

Let's do this:

echo content > Whatever
# content
docker-compose exec SERVICE_NAME cat whatever

echo 'another content' > Whatever

# content
docker-compose exec SERVICE_NAME cat whatever
# another content
docker-compose exec SERVICE_NAME cat Whatever

Expected behavior

I expect caching to work with case-insensitivity:)

Actual behavior

See the example

@thaJeztah

This comment has been minimized.

Copy link
Member

thaJeztah commented Sep 28, 2017

The exec command is executed inside a linux container; Linux is case sensitive, so this is expected, not a bug

@Nondv

This comment has been minimized.

Copy link
Author

Nondv commented Sep 28, 2017

If you are interested in my case:

I edited my Rakefile but rake didnt see changes.
So I looked at rake code and discovered that it looks for rakefile at first

@Nondv

This comment has been minimized.

Copy link
Author

Nondv commented Sep 28, 2017

@thaJeztah
you sure? I thought linux is... linux. And mounted FS is case-insensitive.

Even though. If "linux is case sensitive" then cat whatever should not work at all because there's no such file

@Nondv

This comment has been minimized.

Copy link
Author

Nondv commented Sep 28, 2017

@Nondv

This comment has been minimized.

Copy link
Author

Nondv commented Sep 28, 2017

https://docs.docker.com/docker-for-mac/osxfs/

So case-insensitivity is a feature here but caching it has a bug:)

@dsheets

This comment has been minimized.

Copy link
Contributor

dsheets commented Sep 28, 2017

Local modifications with alternative casing don't properly expire the Linux read cache. Thanks for your report.

@docker-desktop-robot

This comment has been minimized.

Copy link
Collaborator

docker-desktop-robot commented Mar 27, 2018

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

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

@Nondv

This comment has been minimized.

Copy link
Author

Nondv commented May 14, 2018

NOOOO!
/lifecycle frozen

@Nondv

This comment has been minimized.

Copy link
Author

Nondv commented May 14, 2018

@thaJeztah hi!
Can you reopen this issue, please?

adamhooper added a commit to CJWorkbench/cjworkbench that referenced this issue Mar 5, 2019

docker-compose: use 'cached' consistency for bind mounts
Should do two great things:

1. Make OS X / Windows filesystems case-sensitive (which is a bug, but we
   really want it):
    docker/for-mac#320
    docker/for-mac#2096
2. Speed up lots of things on OS X / Windows
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.