Docker-compose - Revision history

Busk at 19:31, 7 September 2024

2024-09-07T19:31:49Z

Busk at 18:29, 26 August 2022

2022-08-26T18:29:22Z

Busk at 05:16, 26 August 2022

2022-08-26T05:16:46Z

Busk at 05:14, 26 August 2022

2022-08-26T05:14:40Z

Busk at 05:13, 26 August 2022

2022-08-26T05:13:54Z

Busk at 23:15, 15 February 2021

2021-02-15T23:15:21Z

Busk at 23:08, 15 February 2021

2021-02-15T23:08:48Z

Busk: Created page with "``` docker-compose up -d --force-recreate ``` -V, --renew-anon-volumes Recreate anonymous volumes instead of retrieving data from the previou..."

2021-02-15T23:08:20Z

Created page with "``` docker-compose up -d --force-recreate ``` -V, --renew-anon-volumes Recreate anonymous volumes instead of retrieving data from the previou..."

New page

```
docker-compose up -d --force-recreate
```
-V, --renew-anon-volumes Recreate anonymous volumes instead of retrieving
data from the previous containers.

← Older revision		Revision as of 19:31, 7 September 2024
Line 1:		Line 1:
		+	# Install from Github Releases
		+	```
		+	version="2.29.2"
		+	curl -LO https://github.com/docker/compose/releases/download/v${version}/docker-compose-linux-x86_64
		+	chmod +x docker-compose-linux-x86_64
		+	sudo mv docker-compose-linux-x86_64 /usr/local/bin/docker-compose
		+	docker-compose -v
		+	```
		+
		+
	Recreate if not there (like after docker network prune)		Recreate if not there (like after docker network prune)
	```		```

@@ Line 9: / Line 9: @@
 - https://stackoverflow.com/questions/54656741/docker-compose-issue-restarting-single-service
 - https://stackoverflow.com/questions/31466428/how-to-restart-a-single-container-with-docker-compose
-Labels
+# Labels
 ```
 It looks like you are using one of the newer versions of docker compose which tracks containers by labels assigned to them rather than by their names. That is why renaming the container didn't work.

@@ Line 4: / Line 4: @@
 docker-compose up -d --force-recreate --build myservice
 ```
 - https://stackoverflow.com/questions/54656741/docker-compose-issue-restarting-single-service

← Older revision		Revision as of 23:15, 15 February 2021
Line 5:		Line 5:
	-V, --renew-anon-volumes Recreate anonymous volumes instead of retrieving		-V, --renew-anon-volumes Recreate anonymous volumes instead of retrieving
	data from the previous containers.		data from the previous containers.
		+
		+
		+	Labels
		+	```
		+	It looks like you are using one of the newer versions of docker compose which tracks containers by labels assigned to them rather than by their names. That is why renaming the container didn't work.
		+
		+	Updating labels
		+	You can check container's labels through the docker inspect command.
		+
		+	$ docker inspect --format='{{json .Config.Labels }}' container_name
		+	The project name is the value of the 'com.docker.compose.project' label.
		+
		+	Moving an existing container to a new project is as easy as changing the value of that label. However it is not yet supported by Docker CLI. There is an open issue requesting that feature.
		+
		+	Workaround
		+	It still can be achieved by directly editing the configuration file of that particular container. There you will find labels currently assigned to that container.
		+
		+	$ nano /var/lib/docker/containers/$container_id/config.v2.json
		+	Assign the new project name to the 'com.docker.compose.project' label and save the file. Next you have to restart the daemon. Otherwise the changes will not be visible to docker.
		+
		+	$ systemctl daemon-reload
		+	```

← Older revision		Revision as of 23:08, 15 February 2021
Line 1:		Line 1:
		+	Recreate if not there (like after docker network prune)
	```		```
	docker-compose up -d --force-recreate		docker-compose up -d --force-recreate

@@ Line 5: / Line 5: @@
 docker-compose up -d --force-recreate --build myservice
 ```
 -V, --renew-anon-volumes   Recreate anonymous volumes instead of retrieving
                                 data from the previous containers.