This is somewhat normal behavior, the way it is structured `dev_install --bootstrap-only` is your best bet and then you need to edit the portage cache file for chromeos-dev-install to switch out the gs:// url for
https://commondatastorage.googleapis.com and then you should be able to install further packages, though there are still some that might have issues due to the fact that this is not really a supported workflow and the expectation is that you would have your own dev server where the packages are being built.