> * By default, Mac file systems are case-insensitive while Linux is case-sensitive.
> On Linux, it is possible to create two separate files: `test` and `Test`,
> while on Mac these filenames would actually refer to the same underlying
> file. This can lead to problems where an app works correctly on a developer's
> machine (where the file contents are shared) but fails when run in Linux in
> production (where the file contents are distinct). To avoid this, Docker Desktop
> insists that all shared files are accessed as their original case. Therefore,
> if a file is created called `test`, it must be opened as `test`. Attempts to
> open `Test` will fail with the error "No such file or directory". Similarly,
> once a file called `test` is created, attempts to create a second file called
> `Test` will fail.
>
> For more information, see [Volume mounting requires file sharing for any project directories outside of `/Users`](/manuals/desktop/troubleshoot-and-support/troubleshoot/topics.md)
#### Shared folders on demand
On Windows, you can share a folder "on demand" the first time a particular folder is used by a container.
If you run a Docker command from a shell with a volume mount (as shown in the
example below) or kick off a Compose file that includes volume mounts, you get a
popup asking if you want to share the specified folder.
You can select to **Share it**, in which case it is added to your Docker Desktop Shared Folders list and available to
containers. Alternatively, you can opt not to share it by selecting **Cancel**.
### Proxies
Docker Desktop supports the use of HTTP/HTTPS and [SOCKS5 proxies](/manuals/desktop/features/networking.md#socks5-proxy-support).
HTTP/HTTPS proxies can be used when:
- Signing in to Docker
- Pulling or pushing images
- Fetching artifacts during image builds
- Containers interact with the external network
- Scanning images
If the host uses a HTTP/HTTPS proxy configuration (static or via Proxy Auto-Configuration (PAC)), Docker Desktop reads