On Fri, 20.02.15 14:11, Peter Paule (systemd-de...@fedux.org) wrote:
heya!
> Here's a small patch for changing the documentation.
Sorry for the late review!
I think this patch is a bit misleading, since "--force" actually drops
the old instance, and that's hardly "updating", that's "replacing w
Here's a small patch for changing the documentation.
add_hint_for_updating_local_dkr_image.patch
Description: Binary data
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Zitat von Lennart Poettering :
If you invoke pull-dkr again, you can remove and replace the writable
snapshot with "--force", or you can simply give it a new name by
specifying it at the end of the command line.
dkr doesn't know the concept of updating containers that have already
been written
On Fri, 20.02.15 12:06, Peter Paule (systemd-de...@fedux.org) wrote:
> Hi,
>
> what needs to be done to update an existing docker image? Pulling it again
> "fails" with "Image '' already exists".
>
> sudo machinectl pull-dkr maxmeyer/test-server --dkr-index-url
> https://index.docker.io --veri
Hi,
what needs to be done to update an existing docker image? Pulling it
again "fails" with "Image '' already exists".
sudo machinectl pull-dkr maxmeyer/test-server --dkr-index-url
https://index.docker.io --verify=no
Enqueued transfer job 1. Press C-c to continue download in background
