Closed Plopix closed 4 years ago
If you are using eZ Launchpad on Mac OS, and you want to migrate to Catalina, just wait.
https://www.firehydrant.io/blog/nfs-with-docker-on-macos-catalina/
We need to redo the mapping from within eZ Launchpad.
Thank you @Webarkitekt who is the one living on the Edge that got first this issue and warned us.
To fix that brand new issue, we will have to change the export path depending on the OS version and the mapping in the docker-composer-osx.yaml.
That will require a new variable but that will be transparent for eZ Launchpad user.
There is a workaround so far:
Change your /etc/exports and your provisioning/dev/docker-compose-osx.yml manually.
/etc/exports
provisioning/dev/docker-compose-osx.yml
I think this is fixed!
https://github.com/ezsystems/launchpad/pull/69
Please review: @Webarkitekt @andrerom @SylvainGuittard @lserwatka
If you are using eZ Launchpad on Mac OS, and you want to migrate to Catalina, just wait.
https://www.firehydrant.io/blog/nfs-with-docker-on-macos-catalina/
We need to redo the mapping from within eZ Launchpad.
Thank you @Webarkitekt who is the one living on the Edge that got first this issue and warned us.
To fix that brand new issue, we will have to change the export path depending on the OS version and the mapping in the docker-composer-osx.yaml.
There is a workaround so far:
Change your
/etc/exports
and yourprovisioning/dev/docker-compose-osx.yml
manually.