This is a follow to the conversation we had during IPFS Thing. I noticed that we didn't update the image namespaces after the repo was migrated to filecoin-project org. The workflows are now failing because the GitHub token that we get doesn't have permission to publish to hammertoe account.
After the merge, the first runs for docker-compose-images-preproofs and docker-compose-images will fail because the updated Dockerfile references ghcr.io/filecoin-project/lotus-localnet-multiarch and ghcr.io/filecoin-project/boost-localnet-multiarch which will only come to existence when boost-localnet-multiarch and lotus-localnet-multiarch finish. If we don't want that to happen, we could split this PR in two - one which will only update the GHA workflows and a second one which will update the Dockerfile.
Awesome! Thank you for following up and working on this. Yes, it would be better to split into two different PRs so that we can first ensure the new build works (and the images work).
This is a follow to the conversation we had during IPFS Thing. I noticed that we didn't update the image namespaces after the repo was migrated to
filecoin-project
org. The workflows are now failing because the GitHub token that we get doesn't have permission to publish tohammertoe
account.After the merge, the first runs fordocker-compose-images-preproofs
anddocker-compose-images
will fail because the updatedDockerfile
referencesghcr.io/filecoin-project/lotus-localnet-multiarch
andghcr.io/filecoin-project/boost-localnet-multiarch
which will only come to existence whenboost-localnet-multiarch
andlotus-localnet-multiarch
finish. If we don't want that to happen, we could split this PR in two - one which will only update the GHA workflows and a second one which will update the Dockerfile.BTW, I've also made you the admin of this repo.