Skip to content
This repository has been archived by the owner on Sep 30, 2024. It is now read-only.

Add workspace volume mode to batch changes troubleshooting doc #23068

Merged
merged 1 commit into from
Jul 21, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions doc/batch_changes/references/troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -140,6 +140,24 @@ docker run --rm --init --workdir /work \

Make sure that you put your `steps.run` command in `/tmp-script` (or any other location), replace `<IMAGE>` with the name of the Docker image, and `/unzipped-archive-locally` (or any other location) with a local copy of the repository in which you want to execute the steps.

### Does it work if you switch to using the workspace mode using Docker volumes?

If executing the `steps` in the batch spec fails with a message that looks similar to this one (i.e. permission error)

```
/bin/sh: can't open '/tmp/tmp.IbdkiA': Permission denied
```

or you're using SELinux or are in a locked-down environment it's possible that Docker bind mounts won't work.

Try using the `-workspace volume` flag (see [`src batch apply`](../../cli/references/batch/apply.md#flags) for a list of all flags) to make `src` use Docker volumes instead:

```
src batch apply -workspace volume -f my-spec.yaml
# or:
src batch preview -workspace volume -f my-spec.yaml
```

## Publishing changesets

### Do you have the right credentials?
Expand Down