$ docker system df

As you can see on the result example : in this case docker is mostly taking storage with the build-cache, almost 57Gb !

Get storage back from images

To get back your storage from docker images i advise you to run « docker image prune -a » wich will delete all non used image on your system.

Get storage back from containers

To get back your contfrom docker containers i advise you to run « docker container prune -a » wich will delete all non running containers on your system. But be really carefull when running this command as it could delete containers that have been stop for multiples reasons.
Before running this command you should always run "docker ps -a » and check there is no stopped container you didn’t know about.

Get storage back from local volumes

To get back your storage from docker volumes you have to run « docker volumes prune -a » wich will delete all non used docker volumes on your system.

Get back storage from build cache

The docker build cache is really good at getting big, as it’s transparent for the user. But each time you build a different layer for your docker container : it’s saved in it !
Then in a matter of week it can get pretty big !

You can get back space of it by running « docker builder prune« 

Looking for a docker GUI ?

Editing docker compose is so much easier with a GUI like Compose Craft, it’s a fully open source docker compose editor ! Not vibe coded ! under MIT licence, Compose Craft help you visualize any docker compose stack !

L’article Docker is taking too much storage ? est apparu en premier sur Composecraft.

First import your docker-compose file in the playground. Then you could see how things are connected together.

If the links look like bellow, so you have to connect the two services to a common network allow them to reach others

So this (upper) look like this (bellow)

Your docker-compose services are connected but can’t reach ?

Have you used the correct hostname ? In the docker-compose bellow, the nginx serice have to use http://backend to reach the backend service and not localhost ! Docker-compose networks have their own DNS.

name: test
services:
  nginx:
    image: nginx:latest
    networks:
      - hephaestus_chick
  backend:
    networks:
      - hephaestus_chick
networks:
  hephaestus_chick:

The hostnames are correct ?

try using the ping cmd from a container to reach the other one. You can use the docker exec to launch a ping from one container to another :

docker exec container_name_nginx ping -c 3 backend

if the container still look to be unreachable, try to inspect the network using :

docker network inspect docker_network_name

That will give you an output like this :

[
  {
    "Name": "dionysus_calf_hephaestus_chick",
    "Id": "039db46f5b3e2a6bd9c4bc322eabd849c1211c979f4faadcb1aa3ecc32d5a509",
    "Created": "2024-12-04T18:07:00.669412851-05:00",
    "Scope": "local",
    "Driver": "bridge",
    "EnableIPv6": false,
    "IPAM": {
      "Driver": "default",
      "Options": null,
      "Config": [
        {
          "Subnet": "192.168.148.0/24",
          "Gateway": "192.168.148.1"
        }
      ]
    },
    "Internal": false,
    "Attachable": false,
    "Ingress": false,
    "ConfigFrom": {
      "Network": ""
    },
    "ConfigOnly": false,
    "Containers": {
      "06fd9566ba0161b8e4a80cf7b84ae27b9d089a355949db5e96075aae31e81f6e": {
        "Name": "dionysus_calf-backend-1",
        "EndpointID": "eae118f0954db6caad3257641f24416621047b5896d8dd4f955d34ec0d9f5b32",
        "MacAddress": "02:42:c0:a8:94:02",
        "IPv4Address": "192.168.148.2/24",
        "IPv6Address": ""
      },
      "9ac2a60d0d80285bfed27da7b5e8ecf991a399b5347d99bd4f002c58c7f90c46": {
        "Name": "dionysus_calf-Nginx-1",
        "EndpointID": "8f1b762e8a8ac18e67d62b5fb7e655e48d91149e9a9bedd58657ffc705a50e9b",
        "MacAddress": "02:42:c0:a8:94:03",
        "IPv4Address": "192.168.148.3/24",
        "IPv6Address": ""
      }
    },
    "Options": {},
    "Labels": {
      "com.docker.compose.network": "hephaestus_chick",
      "com.docker.compose.project": "dionysus_calf",
      "com.docker.compose.version": "2.29.7"
    }
  }
]

Here, under Containers, you can see all connected containers to the network

L’article debug : two docker-compose services can’t connect ? est apparu en premier sur Composecraft.

Note : This work with any other components

How to unlink a service from a newtork in a docker-compose ?

To unlink a service from a network, you can just click on the link then press the backspace key

Note : This work with any other links

L’article How to remove a service from docker-compose ? est apparu en premier sur Composecraft.

In the service editor you can do many things :

The general tab (1) :

In the general tab you can set the image, her tag, the condition restart or command and entry-point for the docker-compose service.

The volume tab (2) :

In the volume tab you can assign new bindings, or edit any linked volumes or binding target inside the container.

Example: the docker volume « data » with the target /var/data will be mounted under /var/data inside the container.

The networking tab (3) :

In the networking tab you mainly can expose service port to the host.

Example: by setting Host port on 8080 and Container one on 80, the localhost:8080 of the host running the docker-compose is forwarded to the container localhost:80 inside the container

The health tab (4) :

The Health tab is more specific and complex, you can refer to the official docker-compose documentation about healthcheck

L’article How to edit a service in a docker-compose ? est apparu en premier sur Composecraft.

From the playground you can click on « share », then a modal with a public link appear. (see bellow)

But you can also share it from the dashboard :

Share a docker-compose from the dashboard

From the dashboard you can click on « … », then on Share. (see bellow)

How to stop sharing a docker-compose ?

Has you may notice, the docker-compose share is accecible to anyone with the link. But how to stop it ? From your share dashboard you can manage all the docker-compose share you made.

Here bellow :

1. Open the share on a webPage
2. Copy the share link to the clipBoard
3. Delete the share (It does not delete the compose, only the share link)

What does a compose craft public share look like ?

A compose craft public share look like the playground but without all the editions utilities :

L’article How to share a docker compose ? est apparu en premier sur Composecraft.

How to add a service to a docker-compose ?

You begin with your first docker-compose in compose craft, or you wonder how to start ? You can just begin by pressing any button highlighted bellow to add a component.

What are the available components for a docker-compose ?

The 5 available types until now are:

1. The networks
2. The environments variables
3. The services
4. The volumes
5. The bindings (what are kind of volumes)

How to save a docker-compose ?

Once you’re happy with your docker compose file you can save it with the « save » button highlighted bellow

L’article The playground est apparu en premier sur Composecraft.

Example: by setting Host port on 8080 and Container one on 80, the localhost:8080 of the host running the docker-compose is forwarded to the container localhost:80 inside the container

L’article How to expose a docker-compose service to the localhost ? est apparu en premier sur Composecraft.