Docker-sync: Syncing problems on 18.03.0-ce-mac59

[fosron]

Error/Feature Requestion/Docs

Sync was working ok (ocassional problems but a docker-sync sync helped). Now with the update of Docker for Mac it stopped working again. I try docker-sync stop && docker-sync start but it would just sync some files generated on the container and not from the host (after a restart would just sync the same files ???). Tried restarting Docker For Mac, but it did not help.

Also when trying to run docker-sync start i get:

May take a long time (15min+) on the first run
          ok  Checking if a newer unison image is available
          ok  No newer image found - current image is up to date.
          ok  Checking if a newer unison image is available
          ok  No newer image found - current image is up to date.
          ok  Starting native_osx for sync applications-docker-sync
applications-docker-sync
unix:///tmp/supervisor.sock no such file
     success  Sync container started
     success  Starting Docker-Sync in the background

before restart of Docker for Mac i got this:

```ok Checking if a newer unison image is available
ok No newer image found - current image is up to date.
ok Checking if a newer unison image is available
ok No newer image found - current image is up to date.
ok Starting native_osx for sync applications-docker-sync
applications-docker-sync
unison: ERROR (no such process)
unison: ERROR (no such process)
success Sync container started

Running `docker-sync sync`:

```docker-sync sync
          ok  Checking if a newer unison image is available
          ok  No newer image found - current image is up to date.
          ok  Checking if a newer unison image is available
          ok  No newer image found - current image is up to date.

(no info in docker-sync logs -f generated)

Docker Driver

Docker For Mac 18.03.0-ce-mac59

Sync strategy

native_osx

your docker-sync.yml

```version: "2"
options:
verbose: false
syncs:
applications-docker-sync: # name of the intermediary sync volume
compose-dev-file-path: 'docker-compose.sync.yml' # docker-compose override file

src: '${APPLICATION}' # host source directory
sync_userid: 1000 # giving permissions to www-data user (as defined in nginx and php-fpm Dockerfiles)
sync_strategy: '${DOCKER_SYNC_STRATEGY}' # for osx use 'native_osx', for windows use 'unison'

sync_excludes: ['.git', 'node_modules', '.idea', 'remote_workspace.php.log', 'remote.php.log'] # ignored directories

monit_enabled: true # not needed, this is the default

# increase tolerance of high cpu if regular syncing uses a lot cpu
monit_interval: 10
monit_high_cpu_cycles: 6

### .env

APPLICATION=../
DOCKER_SYNC_STRATEGY=native_osx
```

OS

macOS High Sierra 10.13.3 (17D47)

[EugenMayer]

Do not expect any fixes for this soonish - rather try to work on this yourself if you want to stick with mac59 - or simpley downgrade to mac42 which is the far best version with docker-sync (for now)

[fosron]

Ah damn, i see...

[EugenMayer]

To clarify the latter statement, i am not going to be part of the hunt for the later d4m edge version and try to fix all issues they bring up during finding "the best way to do something". d4m edge is build as a "use acceptance test" on your computers - see what happens, collect and try againg.

Following those things up all the time, costs a lot of energy, because it is a back and forth. When they bring up a new stable, that changes and then it makes sense to try to onboad docker-sync.

So if you select the edge channel you need to consider that docker-sync will break and there will be no fix until the next stable. If you want to see that change, work on a fix yourself, start PRs and put time into that - but usually that does rather not happen. So i guess we have to deal with the time we have for those kind of projects - and those are limited :)

[mpbarlow]

But 18.03.0-ce-mac59 is stable, it's not an edge version

[EugenMayer]

that is odd, here on my stable channel, the latest release is mac58? is that something broken on my clients? if yes, sorry in advance!

[EugenMayer]

i think this issue is actually related to https://github.com/EugenMayer/docker-sync/issues/553 and will be fixed by 0.5.7 using the new unison image

[mpbarlow]

https://docs.docker.com/docker-for-mac/release-notes/#stable-releases-of-2018

Looks like 59 was released two days ago, possibly a staggered roll out?

[EugenMayer]

Kind of odd, the stable box has mac58 offered just yesterday, my edge box has 59 - so idnk.

[barat]

@EugenMayer - stating that you support only stable is perfectly fine (knowing that as opensource project maintainer you have limited time resources) and I understand this. Maybe write such statement on Wiki/README.md ?
I'm using edge because I hope, that someday bind-mounting won't be close to useless, but because now docker-sync is (sort of) reliable I may switch back to stable :)

[EugenMayer]

@barat i truely have the same hopes, but for now, even the new NFS mount, is just not fast enough and i cannot help it.

State that we support stable only makes a lot of sense truly, but its for the wiki. Not sure where, do you have recommandation? Installation?

[barat]

IMO Installation, or separate "Requirements" where you can write about minimum Mac version, minimum Ram/CPU, Docker for Mac version XXX etc.

[EugenMayer]

@barat what about being bold and just introduce those changes? just help out :)

[EugenMayer]

really odd

[EugenMayer]

very weired, on the client i was on mac58 - that was actually the edge channel, while 59 was the stable one. Ok thats really crazy :D

[EugenMayer]

as expected it was related to https://github.com/EugenMayer/docker-sync/issues/553 and is fixed with 0.5.7 which will be release just right now