docker attach-context configures a Docker context that uses an ephemeral environment.
Usage
Example
1
Create an ephemeral instance
Create an ephemeral instance and note its ID:
Output
2
Attach Docker
Attach your local Docker client to the new environment:
Output
3
Run Docker commands
Use the newly created context to run Docker commands:
Example with Cache Volumes
1
Create an instance with a cache volume
Create a bare instance with a cache volume:
Output
2
Attach Docker
Attach your local Docker context to the remote instance:
3
Mount the cache volume
Run a container and bind mount the cache volume directory into it:Your container can access the cache context at
/cache path. Check how cache volumes work.Options
—new
Create a new ephemeral environment. Either--new or --to <instance-id> must be set.
—to <instance-id>
Rather than creating a new ephemeral environment, attach to Docker in an existing environment (identified by its id). Either--new or --to <instance-id> must be set.
—name <name>
The name of the Docker context that is created; by default it will bensc-{instance-id}.
—state <path>
Specify a custom directory where the command stores the Docker context configuration.—machine_type <cpu>x<mem>
Specifying the machine shape when creating a new environment. The following are the supported machine shapes:2x2: 2 CPU 2 GB memory.2x4: 2 CPU 4 GB memory.4x4: 4 CPU 4 GB memory.4x8: 4 CPU 8 GB memory.4x16: 4 CPU 16 GB memory.16x32: 16 CPU 32 GB memory.
—background
If set, attach to the Docker context in the background. So,nsc docker attach-context does not block the caller.