This repository has been archived on 2024-04-08. You can view files and clone it, but cannot push or open issues or pull requests.
dagger/docs/core-concepts/1203-client.md
user.email d20ffbe8be website: hardcode version banner for 0.1 docs
O.1 docs is deprecated. Let's inform user to switch the the latest version

Signed-off-by: user.email <jf@dagger.io>
2022-04-13 15:58:51 +02:00

1.8 KiB
Raw Blame History

slug displayed_sidebar
/1203/client 0.2

Interacting with the client

dagger.#Plan has a client field that allows interaction with the local machine where the dagger command line client is run. You can:

  • Read and write files and directories;
  • Use local sockets;
  • Load environment variables;
  • Run commands;
  • Get current platform.

Accessing the file system

You may need to load a local directory as a dagger.#FS type in your plan:


Its also easy to write a file locally:


Using a local socket

You can use a local socket in an action:

import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import BrowserOnly from '@docusaurus/BrowserOnly';

{() =>


}

Environment variables

Environment variables can be read from the local machine as strings or secrets, just specify the type:


Running commands

Sometimes you need something more advanced that only a local command can give you:


:::tip You can also capture stderr for errors and provide stdin for input. :::

Platform

If you need the current platform though, theres a more portable way than running uname like in the previous example: