NJ-Greg
commented
3 years ago note - I've verified under my best 'working' installs with two different machines that when I attempt to start a cluster, it starts, but my notebook returns a timeout error rather than success.
Also:
-
disabling the Norton firewall does not resolve the timeout issue for cluster creation, nor does it let coiled install coiled/default work.
-
that Initial work used the CMD.exe prompt from Navigator to reach a DOS terminal window. The PowerShell prompt, so far, gives the same behavior.
More tinkering: "pip install coiled" does work in a newly created anaconda environment (i.e. not base(root)), and an instance of cluster=coiled.cluster(configuration='coiled/default') does generate from a Jupyter notebook with just warnings of version mismatches.
Using ‘conda install -c conda-forge coiled’ in a Windows CMD.exe terminal window under a fresh Anaconda install fails to actually create ‘coiled.exe’. Running pip instead (and before the conda install) succeeds in creating coiled.exe, but tokens must be entered manually (or via a --token parameter using !coiled login from python) for the ‘coiled login’ dialog. However, even then, errors persist. For instance, attempting ‘coiled install coiled/default’ from the CMD.exe terminal fails. There was also a timeout error from attempting to spin up a cluster. Details fully documented in the attached file Coiled Install Under Windows 2021-04-28.pdf .