Here is an example of a where I want to run a yarn install from a specific work

Here is a full demo ! <a href="https://github.com/maximelebastard/pdmlab-docker-co

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/us

run has bad argument order and does not allow usage of composeOptions about docker-compose HOT 7 CLOSED

maximelebastard commented on July 29, 2024

run has bad argument order and does not allow usage of composeOptions

from docker-compose.

Comments (7)

AlexZeitler commented on July 29, 2024 1

Thanks, will look into it this evening.

from docker-compose.

maximelebastard commented on July 29, 2024 1

It works perfectly - thank you for your efficiency

from docker-compose.

AlexZeitler commented on July 29, 2024

It is likely to be a bug. Can you please also share a Dockerfile and docker-compose.yml for easier repro?

from docker-compose.

maximelebastard commented on July 29, 2024

Here is a full demo !
https://github.com/maximelebastard/pdmlab-docker-compose-issue42

Just clone, yarn install and node index.js 😉

Thanks for the quick answer anyway, happy to help if needed

from docker-compose.

AlexZeitler commented on July 29, 2024

@maximelebastard it should now work as expected using this code - as you can see composeOptions have changed to be commandOptions now:

compose.run('some-service', 'cat hello.txt', {
      cwd: path.join(__dirname),
      log: true,
      config: 'docker-compose-42.yml',
      commandOptions: [ '--workdir', '/mountedvolume/nested/dir' ]
    });

We now also have composeOptions which are the global docker-compose CLI options:

compose.run('some-service', 'cat hello.txt', {
      cwd: path.join(__dirname),
      log: true,
      config: 'docker-compose-42.yml',
      composeOptions: [ '--verbose' ],
      commandOptions: [ '--workdir', '/mountedvolume/nested/dir' ]
    });