Found the issue. I was using files which were on the Windows file system (/mnt/d) as from my understanding, files created on the Windows file system can also be used by the Linux Subsystem.
It looks like some of the Linux Ubuntu tools do not like using these shared files.
I am now cloning the Tezos repo straight into the Linux file system.
I believe this is because of a build issue with some OCaml module that checks hardware architecture at build time 😳 This leaks into the Docker images which throws Illegal instruction when run a different arch.
You can read more about it here and here.
The solution is to build the Tezos Docker image yourself on the infra/hardware you want to run it. You ...
I recently wrote and ansible role to do all this on debian machines :
you can check it out here : https://gitlab.com/abate/training-2020-deploy/-/tree/master/ansible
I'm still working on the ssh tunnel that is not super reliable, but the rest seems working.
Here is a step by step updated guide on how to build a Tezos node from the sources on Ubuntu, also see my youtube video:
DOWNLOADS AND LINKS
Tezos node snapshot links:
Available snapshots for main net?
curl -s https://...
I didn't try it but the "normal" way doesn't work?
./tezos-client set delegate for "my_implicit" to "delegate"
Since Babylon, there is no need to "flag" an implicit account as "delegatable"
"In protocol 005, tz accounts which are not registered as delegate can be delegated ...
It gives instructions for installing Tezos (the node, client, and other tools) in various forms: compiling the sources, precompiled binaries, docker containers, etc.