# Galaxy-NG: Remote sync fails "No space left on device"

**URL:** <https://forum.ansible.com/t/galaxy-ng-remote-sync-fails-no-space-left-on-device/5215>\
**Category:** Get Help\
**Tags:** galaxy-ng\
**Created:** [April 30, 2024, 10:09am UTC](https://forum.ansible.com/t/galaxy-ng-remote-sync-fails-no-space-left-on-device/5215 "2024-04-30T10:09:37Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![h-phil](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/h-phil/32/3033_2.png) [@h-phil](https://forum.ansible.com/u/h-phil)\
**Post date:** [April 30, 2024, 10:09am UTC](https://forum.ansible.com/t/galaxy-ng-remote-sync-fails-no-space-left-on-device/5215/1 "2024-04-30T10:09:37Z")

</div>

In my galaxy-ng I want to use the “community” remote to sync two collections from [galaxy.ansible.com](http://galaxy.ansible.com).

In the remote setting I have set the following “YAML requirements”:

```auto
collections:
  - name: community.crypto
    version: ">=2.18.0"
  - name: community.general
    version: ">=8.5.0"

```

When starting the sync I see a lot of json files created in the pulp\_storage/tmp directory.  
After a few hours the “sync” task fails with “[Errno 28] No space left on device”.  
I have 60GB of available disk space before I start the sync. During the sync it is filling up the whole disk with these json files.

I am running the pulp/galaxy:4.9.1 container image from the docker hub via docker-compose.

Have you encountered anything like this?

---

<div class="post-metadata">

**Author:** ![Denney-tech](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/denney-tech/32/1556_2.png) [@Denney-tech](https://forum.ansible.com/u/Denney-tech)\
**Post date:** [April 30, 2024, 3:05pm UTC](https://forum.ansible.com/t/galaxy-ng-remote-sync-fails-no-space-left-on-device/5215/2 "2024-04-30T15:05:08Z")

</div>

Well, I don’t expect 4 collections (2 versions of each) to fill up 60GB, so I’m wondering if your free space is in a different partition from where the sync is going? Or do you actually see the 60GB of free space filling up?

When you run the sync, how many artifacts does the task show it try to download?

 ![image](https://us1.discourse-cdn.com/ansible/original/2X/4/432d65c7f60e3b71b0c1dd7ed390e7b25e7619a5.png)

---

<div class="post-metadata">

**Author:** ![h-phil](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/h-phil/32/3033_2.png) [@h-phil](https://forum.ansible.com/u/h-phil)\
**Post date:** [April 30, 2024, 3:39pm UTC](https://forum.ansible.com/t/galaxy-ng-remote-sync-fails-no-space-left-on-device/5215/3 "2024-04-30T15:39:45Z")

</div>

I first thought so too, but I believe to have mounted the directories correctly.

Part of my docker-compose.yml:

```yaml
services:
  galaxy_ng:
    image: pulp/galaxy:4.9.1
    ports:
      - "80"
    container_name: galaxy_ng
    volumes:
      - ./settings/settings.py:/etc/pulp/settings.py
      - /data/pulp_storage:/var/lib/pulp
      - /data/pgsql:/var/lib/pgsql
      - /etc/ssl/certs/ca-certificates.crt:/etc/ssl/certs/ca-certificates.crt:ro

```

After starting the sync, I can see how the pulp\_storage/tmp is filling up the disk

```bash
root@galaxy:/data# du -h --max-depth=1
43G ./pulp_storage
16K ./lost+found
88M ./pgsql
20K ./certs
44G .

```

```bash
root@galaxy:/data/pulp_storage# du -h --max-depth=1
80K ./.ansible
43M ./media
43G ./tmp
12K ./.local
40K ./.cache
4.0K ./scripts
44G .

```

```bash
root@galaxy:/data/pulp_storage/tmp# find | wc -l
150459

```

In the GUI I just see “running” but no count.

---

<div class="post-metadata">

**Author:** ![Denney-tech](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/denney-tech/32/1556_2.png) [@Denney-tech](https://forum.ansible.com/u/Denney-tech)\
**Post date:** [April 30, 2024, 6:22pm UTC](https://forum.ansible.com/t/galaxy-ng-remote-sync-fails-no-space-left-on-device/5215/4 "2024-04-30T18:22:53Z")

</div>

Sorry @h-phil , I’m not sure what to tell you from here, since I don’t use the compose install. Did you follow the documentation? [Docker compose environment - Galaxy NG](https://ansible.readthedocs.io/projects/galaxy-ng/en/latest/dev/docker_environment/)

---

<div class="post-metadata">

**Author:** ![h-phil](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/h-phil/32/3033_2.png) [@h-phil](https://forum.ansible.com/u/h-phil)\
**Post date:** [May 6, 2024, 12:41pm UTC](https://forum.ansible.com/t/galaxy-ng-remote-sync-fails-no-space-left-on-device/5215/5 "2024-05-06T12:41:41Z")

</div>

@Denney-tech Thanks for the help. I actually found the problem. It is completely unrelated to the galaxy-ng or compose.

The sync was done through a proxy that mistakenly cached API calls and produced this behavior (Cache invalidation problem).