-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
archive/tar: sockets not supported #272
Comments
Is there a github repo somewhere we can try to repro this against? I see some COPY lines in the Dockerfile and I'm not sure what type of files would go there. |
Here is a sample GitHub repo where the error 'archive/tar: sockets not supported' is experienced. https://github.com/dotnet/dotnet-docker/blob/master/samples/dotnetapp/Dockerfile Just add |
Cool, so I was able to reproduce this error
The error comes when trying to get a FileInfoHeader for a socket and adding it to the layer tar, which the tar library doesn't allow. I added logging to see which files were causing this error:
I added code to ignore the socket and built the first stage with Docker and kaniko. The container-diff output was:
I'm not totally sure if these are all files we can ignore, but right now the only thing I can think to do is ignore sockets entirely. Suggestions welcome! |
Yeah I think we should ignore sockets when tarring up the layer. |
Hey @MnrGreg , this should work now, please open another issue if it doesn't! |
Yup, sockets are now skipped and build completes. |
Th issue seems to have re-surfaced in version 1.9 ERRO[0061] Can't add file /data/var/lib/containers/storage/overlay/dbecfc96d215e991ac3c5a84e1c7c31c4ab45cb801ee9c8a160f8f9336ce3758/diff/tmp/CoreFxPipe_MSBuild106 to tar: archive/tar: sockets not supported |
Experiencing the following error during 3rd stage of multistage build (FROM build AS publish):
Dockerfile:
The text was updated successfully, but these errors were encountered: