#Dagger CLI needed for Python SDK

1 messages · Page 1 of 1 (latest)

clear geyser
#

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?

west depot
#

👋 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.

Dagger SDKs make it easy to call the Dagger API from your favorite programming language, by developing Dagger Functions or custom applications.

clear geyser
#

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?

elder lark
#

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)

clear geyser
#

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?

jade gust
clear geyser
#

Thanks @jade gust for the info