Subsequent syncs fail due to destination path not being empty about git-sync HOT 12 CLOSED

v2.0.1 is pushed with better help and an error in this case. PTAL

from git-sync.

Curiously it pushed git-sync-amd64 but not git-sync - will repush

On Sat, Oct 8, 2016 at 1:28 PM, Michael Grosser [email protected]
wrote:

v2.0.1 is not showing up yet. See: https://gcr.io/v2/google_
containers/git-sync/tags/list

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
#8 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFVgVJTg0PgSpYYuU87Z1LI_8VLza0IPks5qx_zigaJpZM4KNt9H
.

from git-sync.

Running into the same issue

from git-sync.

Just as a sidenote the current "workaround" we use is to set GIT_SYNC_ONE_TIME to true and add a command "./git-sync && sleep 999d".
This prevents further syncs, but that is sorta acceptable in our current use case, as we deploy often enough.

from git-sync.

@stp-ip instead of the sleep, you could use pod inits:
http://kubernetes.io/docs/user-guide/production-pods/#handling-initialization

from git-sync.

Yeah that works, if you wanna do only the initial sync. We actually want ongoing sync, but disabled it with GIT_SYNC_ONE_TIME and sleep due to the above bug.

from git-sync.

DEST should be a bare name, "files" not "/path/to/files". 2.0.1 coming up :)

from git-sync.

That's where GIT_SYNC_ROOT comes in. Root basically should be used for the path and DEST should be used as the last folder name. Thanks for clarifying.

from git-sync.

v2.0.1 is not showing up yet. See: https://gcr.io/v2/google_containers/git-sync/tags/list

from git-sync.

Would it be possible to update the demo config to reflect this? It uses GIT_SYNC_DEST as a path rather than bare name.

from git-sync.

send a PR? please :)

from git-sync.

from git-sync.