How to rebuild docker container in docker-compose.yml?

Question

There are scope of services which defined in docker-compose.yml. These service have been started. I need to rebuild only one of these and start it without up other services. I run the following commands:

docker-compose up -d # run all services
docker-compose stop nginx # stop only one. but it still running !!!
docker-compose build --no-cache nginx 
docker-compose up -d --no-deps # link nginx to other services

At the end i got old nginx container. By the way docker-compose doesn't kill all running containers !

Just to clarify upper comment: `docker-compose up --build` rebuild all containers. Use `docker-compose up --build ` as stated in @denov comment. — Jsowa, Sep 20 '20 at 22:22
`docker-compose up --build ` does not work if you have a docker-compose.yml with containers coming from a container-registry — chillwalker, Oct 22 '20 at 16:30
`docker-compose build --no-cache` when you want to build from the first level. — hassanzadeh.sd, Dec 28 '20 at 10:04

score 380 · Answer 1 · edited Jul 31 '20 at 19:10

380

docker-compose up

$ docker-compose up -d --no-deps --build <service_name>

--no-deps - Don't start linked services.

--build - Build images before starting containers.

edited Jul 31 '20 at 19:10

phoenix

3,988
1
29
33

answered Mar 10 '17 at 21:59

denov

7,064
2
23
36

33

`docker-compose build service1 service2 --no-cache` does this job better (https://github.com/docker/compose/issues/1049). I had issue with cached containers that were built before using `docker-compose up -d --no-deps --build ` – evgpisarchik May 31 '17 at 20:37
59

@evgpisarchik The orders a bit out, it should be `docker-compose build --no-cache service1 service2` – Matthew Wilcoxson Mar 27 '18 at 08:10

score 284 · Answer 2 · edited Jul 27 '20 at 13:56

With docker-compose 1.19 up

docker-compose up --build --force-recreate --no-deps [-d] [<service_name>..]

Without one or more service_name arguments all images will be built if missing and all containers will be recreated.

From the help menu

Options:
    -d, --detach        Detached mode: Run containers in the background,
                        print new container names. Incompatible with
                        --abort-on-container-exit.
    --no-deps           Don't start linked services.
    --force-recreate    Recreate containers even if their configuration
                        and image haven't changed.
    --build             Build images before starting containers.

Without cache

To force a rebuild to ignore cached layers, we have to first build a new image

docker-compose build --no-cache [<service_name>..]

From the help menu

Options:
    --force-rm              Always remove intermediate containers.
    -m, --memory MEM        Set memory limit for the build container.
    --no-cache              Do not use cache when building the image.
    --no-rm                 Do not remove intermediate containers after a successful build.

Then recreate the container

docker-compose up --force-recreate --no-deps [-d] [<service_name>..]

I'm confused how this answers the question. How do we rebuild just the one container? — Duncan Jones, Feb 08 '19 at 20:58
You can rebuild only one container by appending it's name to the end of the command. `docker-compose up -d --force-recreate --build container_name` — HarlemSquirrel, Feb 09 '19 at 02:25
Wait a sec, this *recreates **container***, it is not equivalent to `build --no-cache` option, unless the command description is completely wrong — Slav, Mar 28 '20 at 05:58

score 77 · Answer 3 · edited Apr 12 '17 at 13:49

77

This should fix your problem:

docker-compose ps # lists all services (id, name)
docker-compose stop <id/name> #this will stop only the selected container
docker-compose rm <id/name> # this will remove the docker container permanently 
docker-compose up # builds/rebuilds all not already built container

edited Apr 12 '17 at 13:49

tristanbailey

3,945
1
22
29

answered Apr 27 '16 at 09:11

ArgonQQ

1,671
1
8
12

16

if you want to `stop` and `rm` all containers then you can use the command `docker-compose down`. Your solution is better if you only want to get rid of some. – hirowatari Oct 01 '16 at 17:43
1

This solution is a good fit for the setup where you don't want to stop the entire docker application and just recreate one of the services – bluesummers Aug 13 '19 at 13:00
3

I needed to actually run `docker-compose build ` before `up` to rebuild the changed Dockerfile. – Vajk Hermecz Feb 20 '20 at 22:58

score 60 · Answer 4 · answered Oct 27 '18 at 07:22

As @HarlemSquirrel posted, it is the best and I think the correct solution.

But, to answer the OP specific problem, it should be something like the following command, as he doesn't want to recreate ALL services in the docker-compose.yml file, but only the nginx one:

docker-compose up -d --force-recreate --no-deps --build nginx

Options description:

Options:
  -d                  Detached mode: Run containers in the background,
                      print new container names. Incompatible with
                      --abort-on-container-exit.
  --force-recreate    Recreate containers even if their configuration
                      and image haven't changed.
  --build             Build images before starting containers.
  --no-deps           Don't start linked services.

score 21 · Answer 5 · answered Jan 23 '20 at 08:30

21

Maybe these steps are not quite correct, but I do like this:

stop docker compose: $ docker-compose down

remove the container: $ docker system prune -a

start docker compose: $ docker-compose up -d

answered Jan 23 '20 at 08:30

Sergey Ivchenko

872
9
8

12

`docker system prune -a` will delete all images, even ones for other projects. I would recommend against using this. – aL_eX Sep 22 '20 at 17:58
aL_eX, flag -a (means all) you can select only the one you need by specifying its id – Sergey Ivchenko Sep 25 '20 at 10:27
2

@aL_eX I agree this method is somewhat dangerous. But this is working for sure. Other answers do not remove images. – glinda93 Dec 04 '20 at 01:01

score 7 · Answer 6 · answered Jun 18 '20 at 07:02

docker-compose stop nginx # stop if running
docker-compose rm -f nginx # remove without confirmation
docker-compose build nginx # build
docker-compose up -d nginx # create and start in background

Removing container with rm is essential. Without removing, Docker will start old container.

FarhadMohseni · Answer 7 · 2019-07-14T12:56:08.260

5

Simply use :

docker-compose build [yml_service_name]

Replace [yml_service_name] with your service name in docker-compose.yml file. You can use docker-compose restart to make sure changes are effected. You can use --no-cache to ignore the cache.

edited Jul 14 '19 at 12:56

answered Jul 14 '19 at 12:23

FarhadMohseni

166
2
6

score 4 · Answer 8 · answered Apr 27 '16 at 09:17

The problem is:

$ docker-compose stop nginx

didn't work (you said it is still running). If you are going to rebuild it anyway, you can try killing it:

$ docker-compose kill nginx

If it still doesn't work, try to stop it with docker directly:

$ docker stop nginx

or delete it

$ docker rm -f nginx

If that still doesn't work, check your version of docker, you might want to upgrade.

It might be a bug, you could check if one matches your system/version. Here are a couple, for ex: https://github.com/docker/docker/issues/10589

https://github.com/docker/docker/issues/12738

As a workaround, you could try to kill the process.

$ ps aux | grep docker 
$ kill 225654 # example process id

score 3 · Answer 9 · answered Nov 18 '19 at 18:40

For me it only fetched new dependencies from Docker Hub with both --no-cache and --pull (which are available for docker-compose build.

# other steps before rebuild
docker-compose build --no-cache --pull nginx # rebuild nginx
# other steps after rebuild, e.g. up (see other answers)

score -12 · Answer 10 · answered Mar 02 '17 at 18:05

-12

Only:

$ docker-compose restart [yml_service_name]

answered Mar 02 '17 at 18:05

ALEXANDER GOMEZ HIGUITA

127
1
5

5

this will not build new changes. from the manual - If you make changes to your docker-compose.yml configuration these changes will not be reflected after running this command. – denov Mar 10 '17 at 22:00

How to rebuild docker container in docker-compose.yml?

10 Answers10

Without cache

Linked