You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 26, 2021. It is now read-only.
I would like to normalize the file paths stored in the config.json file to always use forward slashes /. Using forward slashes works on all platforms including Windows.
This would allow us to check in the machine configs into version control and share them within a team using different platforms (Linux, OSX, and Windows). Right now, this doesn't work for machines created on a Windows system, because the file paths to the SSH keys HostOptions.AuthOptions.CaCertPath (and corresponding other properties) contain backward slashes \ and the files cannot be opened on non-Windows systems (e.g., certs\\ca.pem).
However, the other way round - creating a machine on a non-Windows system and using the created config.json on a Windows system thereafter - is not a problem...
BTW, I am calling docker-machine with a custom storage path option like this:
docker-machine --storage-path=. create ...
The text was updated successfully, but these errors were encountered:
I would like to normalize the file paths stored in the
config.json
file to always use forward slashes/
. Using forward slashes works on all platforms includingWindows
.This would allow us to check in the machine configs into version control and share them within a team using different platforms (
Linux
,OSX
, andWindows
). Right now, this doesn't work for machines created on aWindows
system, because the file paths to the SSH keysHostOptions.AuthOptions.CaCertPath
(and corresponding other properties) contain backward slashes\
and the files cannot be opened on non-Windows
systems (e.g.,certs\\ca.pem
).However, the other way round - creating a machine on a non-
Windows
system and using the createdconfig.json
on aWindows
system thereafter - is not a problem...BTW, I am calling
docker-machine
with a customstorage path
option like this:The text was updated successfully, but these errors were encountered: