Bug 273569 - sysutils/docker [Patch] PAX cannot encode Devminor
Summary: sysutils/docker [Patch] PAX cannot encode Devminor
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Jochen Neumeister
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-09-04 19:01 UTC by Adam Labus
Modified: 2024-03-11 10:33 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (joneum)


Attachments
Two concatenated patches made with makepatch (1.39 KB, patch)
2023-09-04 19:01 UTC, Adam Labus
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Labus 2023-09-04 19:01:48 UTC
Created attachment 244637 [details]
Two concatenated patches made with makepatch

Currently, the docker port is completely unusable on ZFS, because the docker client mandates the use of the PAX tar format, which causes the following issue:

ERRO[0000] Can't add file /usr/home/hackerman/Desktop/Docker/i4industry_v2/src to tar: archive/tar: cannot encode header: Format specifies PAX; and PAX cannot encode Devminor=4294902015

I wasn't able to replicate this issue in my own GO tar utility, but switching to ext solved it.
A rather naive solution is just to replace it with FormatGNU like in the patch (it seems to work, based on a quick testing). I assume most FreeBSD people use ZFS, in which case any patch is better than none.
Comment 1 Muhammad Moinur Rahman freebsd_committer freebsd_triage 2024-03-11 10:33:22 UTC
What you have done here is you have submitted raw patches to the dists and that does not work like that. When you have your patches you should generate patches by make makepatch which will actually modify the patch files located in files directory. You should submit a git formatted patch of the ports tree not the patch to the dists itself.