devspace: Sync Error - upload archive: upload send: EOF

What happened?
devspace sync fails with Sync Error on /path/to/files: upstream: apply changes: apply creates: upload archive: upload send: EOF.

Log showing the upload failures and then the Sync Error:

[info]   Start syncing
[done] √ Sync started on /Users/jessebye/repos/pronode <-> . (Pod: need-plantations/pronode-579d65f7dd-wz74v)
[info]   Upstream - Handling 1 removes
[info]   Upstream - Upload 1604 create changes (size 10177223)
[info]   Upstream - Retry upload because of error: EOF
[info]   Upstream - Upload 1604 create changes (size 10177223)
[info]   Upstream - Retry upload because of error: EOF
[info]   Upstream - Upload 1604 create changes (size 10177223)
[info]   Upstream - Retry upload because of error: EOF
[info]   Upstream - Upload 1604 create changes (size 10177223)
[info]   Upstream - Retry upload because of error: EOF
[info]   Upstream - Upload 1604 create changes (size 10177223)
[error]  Sync Error on /Users/jessebye/repos/pronode: upstream: apply changes: apply creates: upload archive: upload send: EOF

What did you expect to happen instead?
Local changes should have been uploaded with no error.

How can we reproduce the bug? (as minimally and precisely as possible)
Using devspace version 4.4.0 Try to use devspace sync Observe the issue.

Local Environment:

  • Operating System: mac (Catalina)
  • Deployment method: kubectl apply
  • Devspace version: 4.4.0

Kubernetes Cluster:

  • Cloud Provider: aws
  • Kubernetes Version: version.Info{Major:"1", Minor:"14+", GitVersion:"v1.14.9-eks-c0eccc", GitCommit:"c0eccca51d7500bb03b2f163dd8d534ffeb2f7a2", GitTreeState:"clean", BuildDate:"2019-12-22T23:14:11Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}

Anything else we need to know?
n/a

/kind bug

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 21 (6 by maintainers)

Commits related to this issue

Most upvoted comments

Looks like we got both specific cases solved, the error message has been improved in v4.12 and the docs contain a sync troubleshooting guide now. Closing this for now. Thanks again everyone for helping to narrow these issues down!

@FabianKramm thanks for the tips, we got it to work by setting the user/group to 0! 🎉