Docker Image updaten

Docker Image updaten

Ich habe seit einiger ein Zeit Docker image für den S3 cloudserver laufen, ich wollte heute mal probieren wie man ein Docker Image updated.

Der Container ist gestartet

pi@docker:~/S3 $ docker container ls
CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                    NAMES
81d295a09a05        15ef9ede3b46        "/usr/src/app/docker…"   4 weeks ago         Up 4 weeks          0.0.0.0:8000->8000/tcp   cloudserve

Ich hab das Image selbst aus dem git gebaut, weil es für raspberrpy kein Image gibt. zuerst aktualisier ich ddas git repository

pi@docker:~/S3 $ git pull
remote: Enumerating objects: 202, done.
remote: Counting objects: 100% (202/202), done.
remote: Compressing objects: 100% (10/10), done.
remote: Total 269 (delta 193), reused 198 (delta 192), pack-reused 67
Receiving objects: 100% (269/269), 99.52 KiB | 613.00 KiB/s, done.
Resolving deltas: 100% (206/206), completed with 79 local objects.
From https://github.com/scality/S3
   4332d0a1..fdcbd315  development/8.2                                                      -> origin/development/8.2
 * [new branch]        bugfix/S3C-2502-vault-req-ip-header                                  -> origin/bugfix/S3C-2502-vault-req-ip-header
 * [new branch]        bugfix/S3C-2503-allow-multiple-same-email-address-ACLs-in-single-req -> origin/bugfix/S3C-2503-allow-multiple-same-email-address-ACLs-in-single-req
 * [new branch]        bugfix/S3C-2544-diff-acct-metrics                                    -> origin/bugfix/S3C-2544-diff-acct-metrics
 * [new branch]        bugfix/setup-maven-https-repo                                        -> origin/bugfix/setup-maven-https-repo
   9c524ca9..396f100a  development/7.4                                                      -> origin/development/7.4
   6f0b50a9..8117dd02  development/7.6                                                      -> origin/development/7.6
 * [new branch]        development/7.7                                                      -> origin/development/7.7
   16b65ed2..6b4671b2  development/8.1                                                      -> origin/development/8.1
 * [new branch]        exp/exposeCountItems                                                 -> origin/exp/exposeCountItems
 * [new branch]        exp/perfMetadata                                                     -> origin/exp/perfMetadata
   dfff880a..1b7aa4f7  hotfix/7.4.5                                                         -> origin/hotfix/7.4.5
 * [new branch]        stabilization/7.6.0                                                  -> origin/stabilization/7.6.0
 * [new branch]        w/7.6/bugfix/S3C-2502-vault-req-ip-header                            -> origin/w/7.6/bugfix/S3C-2502-vault-req-ip-header
 * [new branch]        w/7.6/bugfix/S3C-2544-diff-acct-metrics                              -> origin/w/7.6/bugfix/S3C-2544-diff-acct-metrics
 * [new branch]        w/7.7/bugfix/S3C-2502-vault-req-ip-header                            -> origin/w/7.7/bugfix/S3C-2502-vault-req-ip-header
 * [new branch]        w/7.7/bugfix/S3C-2544-diff-acct-metrics                              -> origin/w/7.7/bugfix/S3C-2544-diff-acct-metrics
 * [new branch]        w/8.1/bugfix/S3C-2502-vault-req-ip-header                            -> origin/w/8.1/bugfix/S3C-2502-vault-req-ip-header
 * [new branch]        w/8.1/bugfix/S3C-2544-diff-acct-metrics                              -> origin/w/8.1/bugfix/S3C-2544-diff-acct-metrics
 * [new branch]        w/8.2/bugfix/S3C-2502-vault-req-ip-header                            -> origin/w/8.2/bugfix/S3C-2502-vault-req-ip-header
 * [new branch]        w/8.2/bugfix/S3C-2544-diff-acct-metrics                              -> origin/w/8.2/bugfix/S3C-2544-diff-acct-metrics
 * [new tag]           7.6.0.0_rc1                                                          -> 7.6.0.0_rc1
 * [new tag]           7.4.5.1                                                              -> 7.4.5.1
Updating 4332d0a1..fdcbd315
Fast-forward
 .dockerignore                                       |   3 +-
 Dockerfile                                          |   7 +-
 eve/main.yml                                        |   5 ++
 lib/kms/utilities.js                                |   2 +-
 lib/utilities/aclUtils.js                           |  13 ++--
 package.json                                        |   4 +-
 tests/functional/aws-node-sdk/test/bucket/putAcl.js |  19 +++++
 tests/functional/jaws/pom.xml                       |   4 +-
 tests/unit/api/bucketPutACL.js                      |  44 +++++++++++
 yarn.lock                                           | 451 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-------------------------------------------
 10 files changed, 364 insertions(+), 188 deletions(-)

Aha, neue Commits. Dann lese ich mir genau durch was geändert wurde (ist gelogen ich will hier nur mal probieren wie man den Container aktualisiert)

ich baue ein neues Image

docker build -t cloudserver .
< es folgt sehr viel Output, den ich hier nicht reinschreibe >

ich stoppe den laufenden Container

git stop cloudserver

ich lösche den Container - und jetzt stellt sich wohl jeder die Frage ob wohl alle Daten auf einer persistent Storage sind.

git rm cloudserver

ich starte den Container wieder, dazu habe ich ein kurzen Bash Script.

cloudserver_run.sh

in dem Bashscript stehen alle Startparameter drinnen.
Danach ein kleines Skript gestartet, das den S3 Server testet - haut hin