Open cipherzzz opened 2 weeks ago
Hey @cipherzzz Looks like deployment plans are not the issue here, it fails right from the beginning.
I'm able to make it work following your steps to reproduce (thanks for this beautifully written issue btw 🙏 ). Including:
clarinet deployment apply --deployment-plan-path ./deployments/upgrade.deploy.yaml
error: unable to start bitcoind container: network devnet-feature.devnet is ambiguous (2 matches found on name)
That's the real issue. You could have an container or a volume that still use an volume. Or it could be something else.
If you don't want to spend too much time finding what's wrong docker system prune --all
will prune all your docker and leave it ready to be used (but that's only if you're ok to loose all of your images, volumes, etc)
Hey @cipherzzz Looks like deployment plans are not the issue here, it fails right from the beginning.
I'm able to make it work following your steps to reproduce (thanks for this beautifully written issue btw 🙏 ). Including:
clarinet deployment apply --deployment-plan-path ./deployments/upgrade.deploy.yaml
error: unable to start bitcoind container: network devnet-feature.devnet is ambiguous (2 matches found on name)
That's the real issue. You could have an container or a volume that still use an volume. Or it could be something else. If you don't want to spend too much time finding what's wrong
docker system prune --all
will prune all your docker and leave it ready to be used (but that's only if you're ok to loose all of your images, volumes, etc)
Hey man! Yeah, I can do a docker network prune
for that. The reason it's throwing that is that there is already an instance of clarinet running and the apply
attempts to start another instance. It only starts
an instance for devnet, whereas it simply applies
to testnet and mainnet. I guess what I'd like is a way to apply
changes to an already running devnet.
I guess what I'd like is a way to apply changes to an already running devnet.
It is already the case. The workflow your a describing works and i was able to try and confirm it works
Oh! Ok, awesome I’ll try it again -thanks!
On Sat, Oct 19, 2024 at 11:02 AM Hugo C @.***> wrote:
I guess what I'd like is a way to apply changes to an already running devnet.
It is already the case. The workflow your a describing works and i was able to try and confirm it works
— Reply to this email directly, view it on GitHub https://github.com/hirosystems/clarinet/issues/1576#issuecomment-2423937777, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH57I2Q3QOCSQLVZ536AZLDZ4JX7JAVCNFSM6AAAAABPMMQUO6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRTHEZTONZXG4 . You are receiving this because you were mentioned.Message ID: @.***>
Summary
I'd like to be able to have granular migrations similar to most tooling so that I can test out my migrations and have a well known migration path.
Setup
Fails with
I tried
It fails with the same error What I'd like to be able to do is start the devnet with the specified file and then run
clarinet deployment apply --deployment-plan-path=./deployments/upgrade.deploy.yaml