Hi everyone! I'm using a very old version of the dagger python sdk, 0.8.1, and have a few questions. I'm currently trying to migrate my existing pipelines from our legacy CI/CD platform to a new internal CI/CD platform that has strict network firewall rules. Installing the python sdk through pip works just fine but when I try to run a simple hello world example, i.e Python ci/main.py hello-world, I'm seeing errors indicating that the dagger cli is not able to be downloaded from dl.dagger.io. I'm assuming the dagger cli cannot be downloaded because of the firewall rules the network team has in place. Is the dagger cli needed to run the python sdk?
#Dagger CLI needed for Python SDK
1 messages · Page 1 of 1 (latest)
👋 if you are unable to download/use the CLI. You can try using the Python SDK as a Custom Application that is documented here: https://docs.dagger.io/api/sdk/#custom-applications
That might work better depending upon your use case.
Thank you Jason, I'll give that a try
The documentation does state the use of the dagger cli to run the custom application. Is that the case or can I call the python application i.e ./my-pipeline over the dagger cli?
normally you should be able to run the application directly if the dagger cli is pre-installed.
(but the docs don't mention it so it might not longer work?)
dagger run is most explicit. Either way you need the dagger CLI (it implements cross-language logic reused by all SDKs)
Thanks @elder lark and @west depot for the clarification. I ended up getting the dl.dagger.io added to our allow list for our network. Besides dl.dagger.io or registry.dagger.io, do yall know of any other endpoints that might be needed for dagger to run?
if you're not using modules, there shouldn't be any. We do send some anonymous engine telemetry to api.dagger.cloud so we can understand if / how different version of Dagger are behaving. Also, if you're looking forward to give Dagger Cloud a try, you'll also have add that host to the firewall allow list 🙏
Thanks @jade gust for the info