You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have this block added to the deployment in case there is an issue in EKS similar to the issue described in #879 (comment) but the behavior didn't change. Additionally, I added workingDir: /home/user to see if that would help or not.
I'm not sure where buildkitd is attempting to write the tarball that is being sent to it, I'm guessing there is a permissions issue that can probably be fixed with another emptyDir, but I'm not sure where it needs to be mounted.
The text was updated successfully, but these errors were encountered:
I worked with the copacetic people, the recommended that I talk to buildkitd people because it looked like a buildkitd error. They are sending the tar file, but buildkitd is erroring writing the file. As far as I can tell, it's not a copacetic issue, it's an issue when running buildkitd as deployment+service-rootless.
The error messages are what are logged in buildkitd. It looks like tar/writer.write is throwing an error. Again, I'm assuming it's a permissions issue, I just don't know where to look.
I'm running buildkit in a container in EKS based upon https://github.com/moby/buildkit/blob/master/examples/kubernetes/deployment%2Bservice.rootless.yaml using copacetic in a Jenkins build pipeline.
Running copa, the logs show:
Running buildkit with
--debug --trace
shows:I have this block added to the deployment in case there is an issue in EKS similar to the issue described in #879 (comment) but the behavior didn't change. Additionally, I added
workingDir: /home/user
to see if that would help or not.I'm not sure where buildkitd is attempting to write the tarball that is being sent to it, I'm guessing there is a permissions issue that can probably be fixed with another emptyDir, but I'm not sure where it needs to be mounted.
The text was updated successfully, but these errors were encountered: