#Fyi, I'm about to push several fixes for
1 messages Β· Page 1 of 1 (latest)
ah, one of the fixes being able to use remote modules with dagger shell I'm guessing π
Nope π Just validation issues for building the query with the CLI. Not sure about the remote modules issue with shell.
Do you have an example of that not working? Just so we can create an issue for it
If I run
dagger shell -m github.com/quartz-technology/daggerverse/redis-shell cli --entrypoint /bin/bash
I get
β build "dagger shell" ERROR [2.66s]
β [2.66s] loading module
β asModule ERROR [0.00s]
β’ Engine: 160171b2e275 (version v0.9.0)
β§ 4.42s β 28 β
2 β 2
Error: failed to get loaded module ID: input:1: git.commit.tree.directory.asModule failed to create module from config `.::`: failed to get config file: lstat dagger.json: no such file or directory
but if I
git clone https://github.com/quartz-technology/daggerverse.git quartz-technology-daggerverse
cd quartz-technology-daggerverse/redis-shell
dagger shell cli --entrypoint /bin/bash
It works
looks like user error π or confusing UX @dusk trail @proud comet
β
dagger shell cli --entrypoint /bin/bash -m github.com/quartz-technology/daggerverse/redis-shell
β
dagger shell -m github.com/quartz-technology/daggerverse/redis-shell cli --entrypoint /bin/bash
βοΈ the error looks like the same error when I try to use gale remotely yesterday
same error, the module uses local dependency
I have examples from yesterday. I'll create an issue. Just to. summary of what I know, when we call a module using gitref all dependencies of the repo must be a gitref as well. If module uses a local path as dependency, we're getting this error.
Global flags like -m and --entrypoint won't be able to be used after the first function argument (for now). So they need to be put up to shell.