Hi! I'am trying to use this tutorial for my project, but I'm having problems with the Unison version, in my OSX the installed version is 2.51 and the image of the docker is 2.48. Because of this, when I try to execute the "./m2unison.sh" command, complete the following error:
Testing 'ssh' connection to container... Connection successful Unison profile 'm2devbox-uc-commerce' has been created in '~/.unison'. Now running 'unison -repeat watch m2devbox-uc-commerce' for file syncing mode. Unison 2.51.2 (ocaml 4.06.1): Contacting server... Fatal error: Received unexpected header from the server: expected "Unison 2.51 with OCaml >= 4.01.2\n" but received "Unison 2.48\n\000\000\000\000\017", which differs at "Unison 2.4". This can happen because you have different versions of Unison installed on the client and server machines, or because your connection is failing and somebody is printing an error message, or because your remote login shell is printing something itself before starting Unison.
How can I solve this? I have tried to update the Unision version of the container, but without success. I also tried installing an earlier version of Unison on OSX, but I was not successful either.
Hi! I'am trying to use this tutorial for my project, but I'm having problems with the Unison version, in my OSX the installed version is 2.51 and the image of the docker is 2.48. Because of this, when I try to execute the "./m2unison.sh" command, complete the following error:
Testing 'ssh' connection to container... Connection successful Unison profile 'm2devbox-uc-commerce' has been created in '~/.unison'. Now running 'unison -repeat watch m2devbox-uc-commerce' for file syncing mode. Unison 2.51.2 (ocaml 4.06.1): Contacting server... Fatal error: Received unexpected header from the server: expected "Unison 2.51 with OCaml >= 4.01.2\n" but received "Unison 2.48\n\000\000\000\000\017", which differs at "Unison 2.4". This can happen because you have different versions of Unison installed on the client and server machines, or because your connection is failing and somebody is printing an error message, or because your remote login shell is printing something itself before starting Unison.
How can I solve this? I have tried to update the Unision version of the container, but without success. I also tried installing an earlier version of Unison on OSX, but I was not successful either.