Qnap Container Station

English Container & Virtualization
1

Hi

I created new app via docker compose and I want to update it.

Now I need to “recreate” it and the app will be delete and recreate.

Why isn’t there an option to update the app as you do in docker with the --build flag? That way, the app will be created faster and only the updated components will be recreated.

Thanks!

2

So there’s a couple things to do.

1.) When specifying the docker repository item, be sure to use the tag so that you have the correct version you want. For example, here’s my compose file for SmokePing. See how I have “smokeping:latest” indicated. Now if there’s a new version, it should pull that if the person maintaining the repository has the tags done right.

But… (see below after my compose file)…

smokeping:
    image: lscr.io/linuxserver/smokeping:latest
    container_name: smokeping
    hostname: smokeping #optional
    networks:
      qnet-network:
        ipv4_address: 192.168.1.3
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
      - MASTER_URL=http://192.168.0.3:80/smokeping/ #optional
      - CACHE_DIR=/tmp #optional
    volumes:
      - /share/Container/somokeping/config:/config
      - /share/Container/smokeping/data:/data
    ports:
      - 80:80
    restart: unless-stopped
networks:
  qnet-network:
    driver_opts:
      iface: eth3
    driver: qnet
    ipam:
      driver: qnet
      options:
        iface: eth3
      config:
        - subnet: 192.168.0.0/23
          gateway: 192.168.1.1

2.) Sometimes, even with the tag correct, QNAP seems to not always pull it. That’s because it already has a copy of what it thinks is “smoking:latest.” You need to go to Images in ContainerStation and delete the image that it has stored. In my screenshot below, it has an image named “smokeping:latest” so it may not pull what is actually the latest build from the repository. Delete that and then you should be good to go when you rebuild.

image
image1546×673 118 KB

3

They key here is to use compose and have control over the data storage of your container.

This way you can create,destroy and rebuild a container without losing any data or config.

4

also if you want the recreate to always update the image, then you can add the below line to your compose file. It tell Container station to always download the image.

    pull_policy: always

just remember to prune your images from time to time to get rid of old stuff.

before figuring this out, i had to download the new image, then recreate etc.. this makes it an automated process.

5

OOOOH! This is great! Thank you!

6

i also run WUD with is a docker image watching container. so between that and the recreate working with pull always it super easy to maintain my containers on container station

7

Thanks to all of you!!