So, while this isn’t good news for you, Bryan, I hope your pain will help others avoid the suffering you’re going through.

Still, because of that UNIX thing, I never use slashes in filenames… it normally signifies a folder hierarchy, just like web sites (which often run on a UNIX OS). Well, you know even the Mac OS doesn’t like slashes… but the only character it won’t allow is the colon, which is used internally in the OS (also won’t allow periods at the start of filenames because that turns the file invisible, due to UNIX). I haven’t used this yet, but their site says it can “convert file names to Windows NTFS, SMB, DOS, Mac OS 9” which sounds promising.Īnne-Marie also responded to this issue, writing: I see at that there are several available, including A Better Finder Rename from Public Space. If you have a lot of files to rename (it sounds liked you do), you’ll probably want to use a file-renaming utilty. The first path (Source) is the path in the Docker Container and the second one is the path inside your Local System (Destination). sudo docker run -it -name my-container ubuntu. So the only good way around this is for you to rename those files. Follow the below steps to copy a file from a docker container to a local machine: Step 1: Create a Docker Container. One Web page that explains the differences can be found here. DOS (and subsequently Windows) prohibits a number of special characters in file naming, including the slash. Yes, unfortunately this has been a major problem since the 1980s, when people started moving pages from Mac to PC. But they are unable to copy these links to their harddrive because pc’s don’t recognize them! I had named some of the linked images with the “/” character, like when I was calling out a date, 09/26/07. I ran into a problem when I gave my clients my packaged InDesign files on dvd for their archives and to pull from for new publications.

Mac copy path to a file