Seems like `nitro-node` should work since it has
```yaml
containers:
- cerc/go-nitro
- cerc/nitro-client
```
while `nitro-contracts` only has `nitro-client`?
root@ubuntu-s-4vcpu-16gb-amd-nyc3-01:~# laconic-so --stack ~/cerc/nitro-stack/stack-orchestrator/stacks/nitro-node setup-repositories --git-ssh --pull
Dev Root is: /root/cerc
ERROR: stack /root/cerc/nitro-stack/stack-orchestrator/stacks/nitro-node does not exist
This is what I'm seeing:
```
root@ubuntu-s-4vcpu-16gb-amd-nyc3-01:~# laconic-so --stack ~/cerc/nitro-stack/stack-orchestrator/stacks/nitro-node setup-repositories --git-ssh --pull
Dev Root is: /root/cerc
ERROR: stack /root/cerc/nitro-stack/stack-orchestrator/stacks/nitro-node does not exist
```
Actually I see I was wrong about your change, because after this the go-node image is no longer built from source so the nitro-node stack doesn't need any repos, only nitro-contracts does. It would still be nice to have a CI test but this looks fine.
Actually I see I was wrong about your change, because after [this](https://git.vdb.to/cerc-io/nitro-stack/commit/ceae9fe8d449cada3f6ed0dc235402035d1d3c57) the `go-node` image is no longer built from source so the nitro-node stack doesn't need any repos, only nitro-contracts does. It would still be nice to have a CI test but this looks fine.
You are not authorized to merge this pull request.
This pull request can be merged automatically.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I needed to change one line to get it to work
@@ -93,3 +93,3 @@```bashlaconic-so --stack ~/cerc/nitro-stack/stack-orchestrator/stacks/nitro-node setup-repositories --git-ssh --pulllaconic-so --stack ~/cerc/nitro-stack/stack-orchestrator/stacks/nitro-contracts setup-repositories --git-ssh --pullSeems like
nitro-nodeshould work since it haswhile
nitro-contractsonly hasnitro-client?This is what I'm seeing:
That's really odd. Are you sure the fetch-stack command succeeds and CERC_REPO_BASE_DIR is not set to a different location?
Haven't tested yet, but should double check this
Could you add a workflow to test this?
Actually I see I was wrong about your change, because after this the
go-nodeimage is no longer built from source so the nitro-node stack doesn't need any repos, only nitro-contracts does. It would still be nice to have a CI test but this looks fine.View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.