new images do not transfer but blame me there is no image on server side

[scher200]

Hi dvddarias,

I use the docker-sync to send my docker images to my live server.
But when run a new project and do:
docker-sync user@liveserver.com newprogram:1

it looks like its running and starts saving my image, untill it starts syncing, it quotes:
No Image found on .... serverside somthing.

The thing is the live server has not a lot of images, but that is why i try to sync it.

I read in the project description:

Note: When synchronizing an image on the New list the script will try to look for the highest common parent on your local machine to run the rsync command, so it pays off a lot to use images with the same base image. If no common parent is found the whole image is compressed and transfered.

But i think this is not the case in my example.
Do you have any idea?

[dvddarias]

The docker-sync command is only able to synchronize images from the server
you are connecting to to your local machine, that is moving remote images
to your local machine. It is not a two way syncronization.
In order to do what you want, you have to ssh to your liveserver.com and
run docker-sync there, which usually is not practical thing to do.

On the readme.md this explanation is not explicit, and I should include it.

By the way implementing the feature you want (two way synchronization) is
straight forward, so now that i know that someone needs it, i will
implement it on this weekend, so stay tuned.

On Tue, Jan 19, 2016 at 11:01 AM, scher200 notifications@github.com wrote:

Hi dvddarias,

I use the docker-sync to send my docker images to my live server
But when run a new project and do:
docker-sync user@liveservercom newprogram:1

it looks like its running and starts saving my image, untill it starts
syncing, it quotes:
No Image found on serverside somthing

The thing is the live server has not a lot of images, but that is why i
try to sync it
I read in the project description: Note: When synchronizing an image on
the New list the script will try to look for the highest common parent on
your local machine to run the rsync command, so it pays off a lot to use
images with the same base image If no common parent is found the whole
image is compressed and transfered

But i think this is not the case in my example
Do you have any idea?

—
Reply to this email directly or view it on GitHub
#1.

[scher200]

cool, thanks!

2016-01-21 3:23 GMT+01:00 David Darias notifications@github.com:

The docker-sync command is only able to synchronize images from the server
you are connecting to to your local machine, that is moving remote images
to your local machine. It is not a two way syncronization.
In order to do what you want, you have to ssh to your liveserver.com and
run docker-sync there, which usually is not practical thing to do.

On the readme.md this explanation is not explicit, and I should include
it.

By the way implementing the feature you want (two way synchronization) is
straight forward, so now that i know that someone needs it, i will
implement it on this weekend, so stay tuned.

On Tue, Jan 19, 2016 at 11:01 AM, scher200 notifications@github.com
wrote:

Hi dvddarias,

I use the docker-sync to send my docker images to my live server
But when run a new project and do:
docker-sync user@liveservercom newprogram:1

it looks like its running and starts saving my image, untill it starts
syncing, it quotes:
No Image found on serverside somthing

The thing is the live server has not a lot of images, but that is why i
try to sync it
I read in the project description: Note: When synchronizing an image on
the New list the script will try to look for the highest common parent on
your local machine to run the rsync command, so it pays off a lot to use
images with the same base image If no common parent is found the whole
image is compressed and transfered

But i think this is not the case in my example
Do you have any idea?

—
Reply to this email directly or view it on GitHub
#1.

—
Reply to this email directly or view it on GitHub
#1 (comment)
.

[image: FreeLaunching - Jeroen Schermer] http://freelaunching.nl/

[blueyed]

I would also have hoped for this working more similar to rsync itself, where you typically push changes.

My use case is distributing a single local image to multiple remote hosts, and there is typically no way to access my local machine from the remote server. But this could be done using a ssh tunnel probably then.

[blueyed]

Normal rsync -avP appears to work quite good after all (and is what docker-sync basically does) - must have missed something in the beginning where I've thought that it would re-transfer too much.