How to run postCreateCommand in another folder?

[DanTup]

Currently it seems like postCreateCommand always runs in the folder that was opened, but in the example containers the projects are all in subfolders named test-project. I tried doing this:

"postCreateCommand": ["cd test-project", "pub get"]

But it failed like this:

OCI runtime exec failed: exec failed: container_linux.go:344: starting container process caused "exec: \"cd test-project\": executable file not found in $PATH": unknown
postCreateCommand ["cd test-project","pub get"] failed.

Is there some way to do this? If not, would this be considered?

[Chuxel]

@DanTup You should be able to do this using a string as follows: "postCreateCommand": "cd test-project && pub get" (EDITED)

The array is for separated arguments of a single command. e.g. "postCreateCommand": ["cd", "test-project"]

We can clarify this better in docs looking at it.

[Chuxel]

Whoops! Cmd+Z'd myself into a bad example. Meant: "postCreateCommand": "cd test-project && pub get"

[DanTup]

I tried that but it failed with the same message.

As it turned out, it probably wasn't a good place to do pub get, since this is project-specific, not container-specific. I was really trying it as a workaround until I get to fix Dart-Code/Dart-Code#1719 (the test-project folder being in a subfolder would prevent us noticing it needed packages fetching). With the simplified Dart container there aren't any dependencies now, so I was able to avoid it.

Though now I'm also wondering whether postCreateCommand differs much from just putting an extra RUN section at the bottom of the dockerfile?

[chrmarti]

postCreateCommand can access the mounted folders while RUN cannot. Closing this for now, let us know when it becomes relevant again. (@Chuxel 's suggestion should work.)