![]() with docker compose -profile frontend -profile debug up the profiles frontend and debug will be enabled. You can also enable multiple profiles, e.g. Use -profile to specify one or more active profilesĬalling docker compose -profile frontend up will start the services with the profile frontend and services $ docker compose -p my_project ps -a NAME SERVICE STATUS PORTSĭemo_1 | PING localhost (127.0.0.1): 56 data bytesĭemo_1 | 64 bytes from 127.0.0.1: seq=0 ttl=64 time=0.095 ms Get the postgres image for the db service from anywhere by using the -f flag as follows: ![]() ![]() You can use a command like docker compose pull to Have a compose.yaml file in a directory called sandbox/rails. You can use the -f flag to specify a path to a Compose file that is not located in the current directory, eitherįrom the command line or by setting up a COMPOSE_FILE environment variable in your shell or in an environment file.įor an example of using the -f option at the command line, suppose you are running the Compose Rails sample, and Specifying a path to a single Compose file If you don’t provide this flag on the command line, Compose traverses the working directoryĪnd its parent directories looking for a compose.yaml or docker-compose.yaml file. When stdin is used all paths in theĬonfiguration are relative to the current working directory. Use a -f with - (dash) as the filename to read the configuration from stdin. You can use the -project-directory option to override this base path. ![]() When you use multiple Compose files, all paths in the files are relative to the first configuration file specified ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |