# archive_trailing_data

> Bytes follow the single gzip member.

Bytes follow the single gzip member.

| | |
| --- | --- |
| Kind | Build or validation problem |
| Reported by | Archive validation (registry, room hosts, disko publish) |
| `disko` exit code | 1 (problems) |

Extra bytes follow the end of the single gzip member. The archive must end
exactly where the gzip trailer ends.

## Why it happens

Archive validation reports this code: the registry on upload, and room hosts
before loading. `disko publish` never writes trailing bytes. They usually come
from appending data to the archive after it was built, or from a transfer that
padded the file.

## Wrong

```sh
disko publish --dry-run --out release.tgz
echo "notes" >> release.tgz
```

## Right

```sh
disko publish --dry-run --out release.tgz
```

## See also

- [Publish a release](/get-started/publish)
- [`archive_gzip_multi_member`](/errors/archive_gzip_multi_member)