Docker compose updates

[rosieyohannan]

Description

• Update instruction for installing Docker Compose in a non cimg image
• Refer to the latest version of compose by using docker compose

Reasons

Customer confusion around docker-compose / docker compose

Content Checklist

Please follow our style when contributing to CircleCI docs. Our style guide is here: https://circleci.com/docs/style/style-guide-overview.

Please take a moment to check through the following items when submitting your PR (this is just a guide so will not be relevant for all PRs) 😸:

• Break up walls of text by adding paragraph breaks.
• Consider if the content could benefit from more structure, such as lists or tables, to make it easier to consume.
• Keep the title between 20 and 70 characters.
• Consider whether the content would benefit from more subsections (h2-h6 headings) to make it easier to consume.
• Check all headings h1-h6 are in sentence case (only first letter is capitalized).
• Is there a "Next steps" section at the end of the page giving the reader a clear path to what to read next?
• Include relevant backlinks to other CircleCI docs/pages.

[DominicLavery]

Not directly related to your change, but whilst we are in the area:
We probably shouldn't recommend pinned version and instead should give examples with the current tag instead

[DominicLavery]

The remote docker daemon runs on a different system than the docker CLI and docker compose
This isn't strictly true now. Remote docker jobs now run on a machine executor, and that is where we spin up the jobs containers. The daemon is running on the same executor. I don't know if this can be reworded somehow to leave out such details 😖 Maybe it doesn't matter for your purposes here

[rosieyohannan]

Yes I wondered about this - so is the whole explanation of moving data aropund to make it accessible outdated now?

This section is there to point out differences (that users need to be aware of) around using docker compose and the docker executor as an alternative to using docker compose and the machine executor. If this info is now irrelevant I can just remove it

[DominicLavery]

I suppose it does do that. It is perhaps a bit academic. I see the section has only moved as well. So, I'll give this a stamp

[sebastian-lerner]

👋 i am talking to a prospective customer and they pointed me to this paragraph as a reason for why they couldnt achieve the thing they wanted with remote docker.

i had the same reaction as you @DominicLavery which is that this wording is outdated because remote docker is basically machine now. if i open up a PR to edit the language, any guidance for what to remove Dom? definitley the pieces about "remote engine" and "remote docker daemon runs on a different system". any idea if the person still needs to do the docker cp stuff? i would assume no but the user i'm talking to said that it didnt work for them

"The issue I was referring to about docker is that as part of the deploy we run a command in a docker container (which has encapsulated some generic infrastructure setup) that requires as input a configuration file accessed via a bind mounted volume. Something like:

docker run -v ./config.yaml:/app/config.yaml ... image

This did not work"

also let me know if you want me to post and tag ask-execution for this question instead. the user did manage to get things working using docker cp so maybe that is still needed for some reason.

[DominicLavery]

RE: docker cp
It doesn't really change anything around where the data lives. They still run in a primary docker container and so still might need to copy data around. A volume mount would occur on the hosts file system, not the primary containers so the config file or other data they would be after likely wouldn't be there

[sebastian-lerner]

#9170 lmk what you think

[sebastian-lerner]

🚀