Despite reading the doc, I still | Dagger | Page 1

Hi! 👋
tl;dr If you're just getting started, very likely dagger call is going to be the right choice. It's the new/current approach. You can call all of the functions in https://daggerverse.dev/ or ones you write yourself 🙂

dagger call is used to call Dagger functions (within Dagger modules) from the CLI. It's the "new way". Functions are cross-language. So in addition to calling them from the CLI, you can dagger install a module of functions that were written in TypeScript (for example) into your Dagger pipeline module you're writing in Python and invoke those functions from code too! Dagger functions run sandboxed from the host for added security.
Example of a module (in git) with one function (hello):

$dagger -m github.com/shykes/daggerverse/hello@v0.1.2 functions
Name    Description
hello   Say hello to the world!

$ dagger -m github.com/shykes/daggerverse/hello@v0.1.2 call hello
hello, world!

dagger run is mostly used to run standalone programs that import a Dagger SDK package for a language ecosystem (e.g. Go, Node.js, Python). These programs are single-language (use the language's facility for packages/imports) and run on the host machine, which can make file access easy, but is less secure.
Example invocations:

dagger run go run main.go
dagger run node index.mjs
dagger run python main.py

Daggerverse

Discover and share modules full of Dagger functions encapsulating the community's devops knowledge

#Despite reading the doc, I still