Upgrades binaries.
- Alpine 3.3 -> 3.4 - PyDrive 1.0.1 -> 1.2.1 - Removes some layers.
This commit is contained in:
11
Dockerfile
11
Dockerfile
@@ -1,9 +1,9 @@
|
|||||||
FROM alpine:3.3
|
FROM alpine:3.4
|
||||||
|
|
||||||
RUN apk add --update duplicity openssh openssl py-crypto py-pip rsync \
|
RUN set -x \
|
||||||
&& pip install pydrive==1.0.1 \
|
&&apk add --no-cache duplicity openssh openssl py-crypto py-pip rsync \
|
||||||
|
&& pip install pydrive==1.2.1 \
|
||||||
&& apk del --purge py-pip \
|
&& apk del --purge py-pip \
|
||||||
&& rm /var/cache/apk/* \
|
|
||||||
&& adduser -D -u 1896 duplicity \
|
&& adduser -D -u 1896 duplicity \
|
||||||
&& mkdir -p /home/duplicity/.cache/duplicity \
|
&& mkdir -p /home/duplicity/.cache/duplicity \
|
||||||
&& mkdir -p /home/duplicity/.gnupg \
|
&& mkdir -p /home/duplicity/.gnupg \
|
||||||
@@ -11,8 +11,7 @@ RUN apk add --update duplicity openssh openssl py-crypto py-pip rsync \
|
|||||||
|
|
||||||
ENV HOME=/home/duplicity
|
ENV HOME=/home/duplicity
|
||||||
|
|
||||||
VOLUME /home/duplicity/.cache/duplicity
|
VOLUME ["/home/duplicity/.cache/duplicity", "/home/duplicity/.gnupg"]
|
||||||
VOLUME /home/duplicity/.gnupg
|
|
||||||
|
|
||||||
USER duplicity
|
USER duplicity
|
||||||
|
|
||||||
|
|||||||
@@ -1,4 +1,4 @@
|
|||||||
[](https://imagelayers.io/?images=wernight/duplicity:latest 'Get your own badge on imagelayers.io')
|
[](https://microbadger.com/images/wernight/duplicity "Get your own image badge on microbadger.com")
|
||||||
|
|
||||||
Dockerized **[duplicity](http://duplicity.nongnu.org/)** backup tool.
|
Dockerized **[duplicity](http://duplicity.nongnu.org/)** backup tool.
|
||||||
|
|
||||||
@@ -18,7 +18,7 @@ For the general command-line syntax, do:
|
|||||||
In general you...
|
In general you...
|
||||||
|
|
||||||
* Must mount what you want to backup or where you want to restore a backup.
|
* Must mount what you want to backup or where you want to restore a backup.
|
||||||
* Should mount `/home/duplicity/.cache/duplicity` as writable somewhere (if not cached, [duplicity will have to recreate it from the remote repository which may require decrypting the backup contents](http://duplicity.nongnu.org/duplicity.1.html#sect5)).
|
* Should mount `/home/duplicity/.cache/duplicity` as writable somewhere (if not cached, [duplicity will have to recreate it from the remote repository which may require decrypting the backup contents](http://duplicity.nongnu.org/duplicity.1.html#sect5)). Note it may be quite large and contains metadata info about files you've backed up in clear text.
|
||||||
* Should mount `/home/duplicity/.gnupg` as writable somewhere (that directory is used to validate incremental backups and shouldn't be necessary to restore your backup if you follows steps below).
|
* Should mount `/home/duplicity/.gnupg` as writable somewhere (that directory is used to validate incremental backups and shouldn't be necessary to restore your backup if you follows steps below).
|
||||||
* Should specify duplicity flag `--allow-source-mismatch` because Docker has a random host for each container.
|
* Should specify duplicity flag `--allow-source-mismatch` because Docker has a random host for each container.
|
||||||
* Could set environment variable `PASSPHRASE`, unless you want to type it manually in the prompt (remember then to add `-it`).
|
* Could set environment variable `PASSPHRASE`, unless you want to type it manually in the prompt (remember then to add `-it`).
|
||||||
|
|||||||
Reference in New Issue
Block a user