When bootstrapping with 2.2 the client appears to be querying streams.canonical.com to identify the proper version of tools to download and then download them. For some reason, if streams.c.c is accessible via http then the bootstrap doesn't throw an error, but can't download the packaged tools so it uses a locally built version. This is fine if all your nodes are the same architecture as the deployment host, but causes problems if they aren't.
It would be good to get at least a warning during the bootstrap if the client is unable to connect properly to streams.c.c or, alternatively, provide a reason that the bootstrap is falling back to a locally built version of the tools when it does so. Some way to identify what's happening in this situation that doesn't involve the user bootstrapping somewhere else and comparing the two sets of outputs. Even a warning in the debug output if it can't contact streams.c.c for either the tools query or download would be great if you don't want to pollute the non-debug output.
I have the feeling we are probably checking from the client what is available, but ultimately the download to the target machine is done from the target machine. Just because your laptop can see streams.