starred/Docker-OSX
1
0
Fork 0
mirror of https://github.com/sickcodes/Docker-OSX.git synced 2026-01-11 21:10:25 +01:00
Code Issues 411 Packages Projects Releases Wiki Activity

Mounting an exFAT drive from Ubuntu onto OSX #98

New Issue
Closed
opened 2025-12-28 23:24:13 +01:00 by adam · 5 comments
adam commented 2025-12-28 23:24:13 +01:00
Owner
Copy Link

Originally created by @thematrixdev on GitHub (Dec 29, 2020).

On my computer, Ubuntu is installed on a NVMe-SSD drive. Docker-OSX Docker version is installed on the same drive.

There is another 2.5" SATA SSD dirve on my computer. I have formated it to be exFAT, so both Ubuntu and OSX can read the data from it. It is mounted in /media/me/SSD on Ubuntu; and onto OSX by adding -hda /dev/sde onto docker-compose.yml.

To make sure the drive is really mounted, I have placed several files onto the drive before running docker-compose up. After OSX is installed and booted, the drive "SSD" is shown up in the Finder. The several test files exist.

However, after I have tried putting some more files from Ubuntu, the newly added files are now shown up in OSX. And putting some files from OSX, they don't show up in Ubuntu neither.

  1. default -hda mounting should be read-only on the guest OS? I want it to be read-only on the guest OS actually
  2. why the drive is mounted, but showing different content? the mounted drive shows correct filesystem format and disk size.

Thanks.

Originally created by @thematrixdev on GitHub (Dec 29, 2020). On my computer, Ubuntu is installed on a NVMe-SSD drive. Docker-OSX Docker version is installed on the same drive. There is another 2.5" SATA SSD dirve on my computer. I have formated it to be exFAT, so both Ubuntu and OSX can read the data from it. It is mounted in /media/me/SSD on Ubuntu; and onto OSX by adding `-hda /dev/sde` onto `docker-compose.yml`. To make sure the drive is really mounted, I have placed several files onto the drive before running `docker-compose up`. After OSX is installed and booted, the drive "SSD" is shown up in the Finder. The several test files exist. However, after I have tried putting some more files from Ubuntu, the newly added files are now shown up in OSX. And putting some files from OSX, they don't show up in Ubuntu neither. 1. default -hda mounting should be read-only on the guest OS? I want it to be read-only on the guest OS actually 2. why the drive is mounted, but showing different content? the mounted drive shows correct filesystem format and disk size. Thanks.
adam closed this issue 2025-12-28 23:24:13 +01:00
adam commented 2025-12-28 23:24:15 +01:00
Author
Owner
Copy Link

@sickcodes commented on GitHub (Dec 29, 2020):

Hey!

I haven't used the Docker compose file but I believe it could be out of date.

The compose file was added a few months ago and a few things have changed, does it work using the normal commands?

@sickcodes commented on GitHub (Dec 29, 2020): Hey! I haven't used the Docker compose file but I believe it could be out of date. The compose file was added a few months ago and a few things have changed, does it work using the normal commands?
adam commented 2025-12-28 23:24:15 +01:00
Author
Owner
Copy Link

@thematrixdev commented on GitHub (Dec 30, 2020):

I have just try to update the docker-compose after reading the single command, seems no difference.

It seems the external harddisk is read at the very beging, the state is kept, and the disk is cloned and separated. Even I erase the disk in OSX, the data is still there on the host. So strange...

@thematrixdev commented on GitHub (Dec 30, 2020): I have just try to update the docker-compose after reading the single command, seems no difference. It seems the external harddisk is read at the very beging, the state is kept, and the disk is cloned and separated. Even I erase the disk in OSX, the data is still there on the host. So strange...
adam commented 2025-12-28 23:24:15 +01:00
Author
Owner
Copy Link

@sickcodes commented on GitHub (Jan 6, 2021):

Correct me if I'm wrong, but won't the OSX disk be created in created in /var/lib/docker/volumes?

@sickcodes commented on GitHub (Jan 6, 2021): Correct me if I'm wrong, but won't the OSX disk be created in created in `/var/lib/docker/volumes`?
adam commented 2025-12-28 23:24:16 +01:00
Author
Owner
Copy Link

@mrkvn commented on GitHub (Jan 9, 2021):

@thematrixdev I'm curious. Can you post here the docker-compose.yml you're using?

@mrkvn commented on GitHub (Jan 9, 2021): @thematrixdev I'm curious. Can you post here the `docker-compose.yml` you're using?
adam commented 2025-12-28 23:24:16 +01:00
Author
Owner
Copy Link

@sickcodes commented on GitHub (Mar 14, 2021):

Added arbitrary disk passthrough in 2295eef68f

Please see examples here: https://github.com/sickcodes/Docker-OSX#mount-a-disk-inside-osx-from-the-host

@sickcodes commented on GitHub (Mar 14, 2021): Added arbitrary disk passthrough in https://github.com/sickcodes/Docker-OSX/commit/2295eef68fb180d9021bb50b8244cdead3c1531d Please see examples here: https://github.com/sickcodes/Docker-OSX#mount-a-disk-inside-osx-from-the-host
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
enhancement
following upstream developments
good first issue
help wanted
invalid
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/Docker-OSX#98
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?