Ignore update check for built containers

[randellhodges]

I'm not sure if there is an option already, so I thought I'd post this as a question first.

In one of my docker compose files, I have "built" container. This just basically builds a small debian container that does some file watcher stuff. I could push it into my local repository and pull it there, but that seems like a hassle for something small.

  watch-env:
    container_name: watch-env
    network_mode: none
    build: watch-env/
    volumes:
      - /docker/stacks:/docker/stacks

However, for this one container, Arcane keeps checking docker for updates, but that isn't going to work:

Maybe thru the use of a label or using a pull_policy: never or something, Arcane would recognize that it shouldn't try anything with that one container?

[randellhodges]

Hmm, I wasn't thinking really when I posted this. I'm thinking you'd need to someone use docker image inspect and see if there is anything inside that to determine if it should be ignored and not any compose labels or properties.

Edit: After further reflection, I suppose the label could be in the Dockerfile and then it would be available in the docker image inspect results. Not as "portable" as I was hoping.

Edit 2: Well, labels can be in the docker compose file (and used when building) as well (learn something new everyday), so that might be a "little" better

[sheikhfarhan]

@randellhodges Hi, you managed to figure this out? Im having the same with the caddy build with custom plugins.

When using WUD (What's Up Docker), I added a label within the service I dont want WUD "check/look" like so:

# WUD cannot check it on Docker Hub (prevents 401 errors).
   labels:
     - "wud.watch=false"

Is there something similar I can do for Arcane?

[randellhodges]

I didn't look at the source, but it looks like you verified that labels are the way to handle it. I'm guessing that at the moment there is no support for this in Arcane.