Is there any reason to use start a docker container without using compose?

I have always run docker containers using

docker-compose

docker-compose

, even if it's just a single container. But every guide I see for dockerizing things includes instructions for how to build and run the container without compose, something like

docker build -t ct3a-docker --build-arg NEXT_PUBLIC_CLIENTVAR=clientvar .
docker run -p 3000:3000 -e DATABASE_URL="database_url_goes_here" ct3a-docker

docker build -t ct3a-docker --build-arg NEXT_PUBLIC_CLIENTVAR=clientvar .
docker run -p 3000:3000 -e DATABASE_URL="database_url_goes_here" ct3a-docker

What is the use case for this?

TTC

Theo's Typesafe Cult•4y ago

cje

Is there any reason to use start a docker container without using compose?

I have always run docker containers using

docker-compose

docker-compose

, even if it's just a single container. But every guide I see for dockerizing things includes instructions for how to build and run the container without compose, something like

docker build -t ct3a-docker --build-arg NEXT_PUBLIC_CLIENTVAR=clientvar .
docker run -p 3000:3000 -e DATABASE_URL="database_url_goes_here" ct3a-docker

docker build -t ct3a-docker --build-arg NEXT_PUBLIC_CLIENTVAR=clientvar .
docker run -p 3000:3000 -e DATABASE_URL="database_url_goes_here" ct3a-docker

What is the use case for this?

Is there any reason to use start a docker container without using compose?

Similar Threads

Is there any reason to use start a docker container without using compose?

Similar Threads

Similar Threads

Similar Threads