Skip to main content
DockerCustomer feedback

An embedded firmware developer using Docker on Azure DevOps for three years reports challenges with tag reliability, image complexity, and managing storage costs for 20GB images under 10-15 year...

Source: Autobound Signal API · 80 signals tracked for Docker · updated

Get Docker's live signals in Claude or ChatGPT, or by API

AskWhat changed at Docker this week? Use Autobound signals for docker.com.

What happened

An embedded firmware developer using Docker on Azure DevOps for three years reports challenges with tag reliability, image complexity, and managing storage costs for 20GB images under 10-15 year safety compliance retention rules.

Source

RedditNov 6, 2026By u/vaugsantos90

r/docker

Question over general docker usage/concept

upvotes
2
comments
11

Post

Greetings, I would like to share a problem that I'm facing with Docker, looking for some ideas. In our company we've started to use docker hosted in an Azure DevOps cloud ubuntu machine, there we have an Azure self-hosted agent installed. We work only with firmware projects and this is our build server. We have this setup for 3 years. Usually, I generate the docker images on demand according with the project requirements.In our firmware projects hosted in git we have a yaml pipeline configuration where we set the image tag so that the proper container can be raised to process the build. We have a requirement from safety standards (we must keep the project artifacts/infrastructure from 10 to 15 years), because of that I keep all the dependencies I need to reproduce/re-create an image as debian installers (for offline installation). I've created a script which runs prior the build process, which creates a yaml manifest containing all the image packages and include this manifest also in the image (at /etc/manifest.yaml) for runtime check. Then it's possible to verify the content via the manifest hash. Examples of dependencies we have are cmake, unit test tools, static code analyzer, and so on.We decided to keep everything in a single image because most of the tools require the compiler, so that the image complexity keeps lower as possible. As we have different projects...

Keep reading with a free account

The rest of this post, and every signal for Docker, is in your free account.

Extracted from these lines

  • As our concept is based on tags, and the docker tags are not the most reliable thing in the world, I keep also the tagged image name as a LABEL within the image.

    From the post

  • At this point I ask myself if we are going in the right direction and the increased complexity in the toolchain management is because of the concept we've decided to go for

    From the post

  • Note: I know that I can save the image in a registry, in parallel I'm trying to find solutions (if possible) to reduce storage costs (each image ~20GB).

    From the post

Comments on the post

5 of 11 comments
  • “Your pipeline should push your image in a registry like Nexus for example. Then just backup Nexus VM for your 15 years retention with your RTO/RPO policy.”

    u/xanyook3 points · Nov 6, 2026View

  • “You sure you understand what an image is? Why do you need to "keep track of artifact used to create an image"? An image IS the artifact used to create a container. It's like saying "I need to create a version control tool to so that i can re-create my git repo history"”

    u/Lumethys2 points · Nov 6, 2026View

  • “I’m not in the same position as you, but maybe the way I see it is that docker should be a great asset. Why worry about labels etc, can you not just keep the built image? Or is your issue more about how you tie the built images to certain ci runs so you know what image built what code?”

    u/Perfect-Escape-39041 points · Nov 6, 2026View

  • “Having a pattern that's easy to follow is good. Having config/build process in source control is good Having build dependencies captured is good. Having git tags that relate to the container images is good, having them be immutable would be better. We use the 'git describe --tags --long --always' value when tagging container images because it includes part of the commit hash string and can”

    u/crackjiver1 points · Nov 6, 2026View

  • “Hi there! I don't see a problem with keeping the dependencies needed for an offline rebuild. That perfectly makes sense. One thing I'd change is how you identify the image used by each build. Copying the tag into a LABEL doesn't stop that tag from pointing to another image later. Keep the readable tag, but record the image digest alongside the source commit in your build records. At least that”

    u/Fun-Adhesiveness-3621 points · Nov 6, 2026View

Extracted by Autobound

From the Signal API record
Signal
Customer feedback

What this signalsUser posts often show product pain before it reaches reviews or churn.

Subreddit
r/docker
Event date
Nov 2026

Companies

  • Azure DevOpsAlso named
  • Sonatype NexusAlso named

The full record

From the Signal API record

Numbers

Mentions
2

Details

Timing
Ongoing state
Category
Usability
Virality
Low
Post kind
Text
Prominence
Core
Company's role
Vendor

Topics and mentions

Topics

  • containers
  • compliance
  • ci/cd
  • devops

Products named

  • Docker

Extraction

Sentiment
Mixed
Detected
Nov 6, 2026
signal_type
reddit-company
signal_subtype
customerFeedback

Use this data

Get every Reddit signal for Docker and the companies you sell to, in the tools you already use.

  1. Ask Claude about it

    Connect Autobound to Claude, Claude Code or Cursor with MCP. Then ask: “What changed at Docker this week?”

  2. Send it to your own tools

    The Signal API returns Reddit signals for any list of companies as JSON, for your CRM, warehouse or app.

  3. Try it free

    Sign up and spend your free credits on the companies you sell to.

    Start Free1,000 free credits

The API returns more than this page shows

This page shows a preview. The full reddit-company record in the Signal API and MCP can also have these 8 fields. Some fields are empty for some signals.

Company

  • linkedin_urlValue in the API
  • industriesValue in the API
  • employee_count_lowValue in the API
  • employee_count_highValue in the API
  • revenueValue in the API
  • descriptionValue in the API

Signal

  • signal_nameValue in the API
  • associationValue in the API
Show the full JSONThe record on this page and the API request

GET /v1/signals/dabb66b3-cde8-5c6c-abec-c63584840482 returns this record as JSON. POST /v1/companies/enrich returns every signal for docker.com.

{
  "signal_id": "dabb66b3-cde8-5c6c-abec-c63584840482",
  "signal_type": "reddit-company",
  "signal_subtype": "customerFeedback",
  "detected_at": "2026-11-06T19:09:25+00:00",
  "company": {
    "name": "Docker",
    "domain": "docker.com"
  },
  "data": {
    "nsfw": false,
    "stage": "none",
    "awards": 0,
    "timing": "ongoing_state",
    "topics": [
      "containers",
      "ci/cd",
      "compliance",
      "devops"
    ],
    "post_id": "1xplb98",
    "summary": "An embedded firmware developer using Docker on Azure DevOps for three years reports challenges with tag reliability, image complexity, and managing storage costs for 20GB images under 10-15 year safety compliance retention rules.",
    "category": "usability",
    "comments": [
      {
        "url": "https://www.reddit.com/r/docker/comments/1xplb98/comment/19s8svxhzvso1/",
        "depth": 0,
        "score": 3,
        "author": "xanyook",
        "excerpt": "Your pipeline should push your image in a registry like Nexus for example. Then just backup Nexus VM for your 15 years retention with your RTO/RPO policy.",
        "posted_at": "2026-11-06T20:49:30.000Z",
        "author_url": "https://www.reddit.com/user/xanyook/"
      },
      {
        "url": "https://www.reddit.com/r/docker/comments/1xplb98/comment/19s8pexihkgkj/",
        "depth": 0,
        "score": 2,
        "author": "Lumethys",
        "excerpt": "You sure you understand what an image is? Why do you need to \"keep track of artifact used to create an image\"?\n\n An image IS the artifact used to create a container.\n\n It's like saying \"I need to create a version control tool to so that i can re-create my git repo history\"",
        "posted_at": "2026-11-06T19:31:39.000Z",
        "author_url": "https://www.reddit.com/user/Lumethys/"
      },
      {
        "url": "https://www.reddit.com/r/docker/comments/1xplb98/comment/19s8phy1qqnz4/",
        "depth": 0,
        "score": 1,
        "author": "Perfect-Escape-3904",
        "excerpt": "I’m not in the same position as you, but maybe the way I see it is that docker should be a great asset. Why worry about labels etc, can you not just keep the built image?\n\n Or is your issue more about how you tie the built images to certain ci runs so you know what image built what code?",
        "posted_at": "2026-11-06T19:33:32.000Z",
        "author_url": "https://www.reddit.com/user/Perfect-Escape-3904/"
      },
      {
        "url": "https://www.reddit.com/r/docker/comments/1xplb98/comment/19s8pim0g676s/",
        "depth": 0,
        "score": 1,
        "author": "crackjiver",
        "excerpt": "Having a pattern that's easy to follow is good.\n\n Having config/build process in source control is good\n\n Having build dependencies captured is good.\n\n Having git tags that relate to the container images is good, having them be immutable would be better.\n\n We use the 'git describe --tags --long --always' value when tagging container images because it includes part of the commit hash string and can",
        "posted_at": "2026-11-06T19:33:57.000Z",
        "author_url": "https://www.reddit.com/user/crackjiver/"
      },
      {
        "url": "https://www.reddit.com/r/docker/comments/1xplb98/comment/19s9127kthd5x/",
        "depth": 0,
        "score": 1,
        "author": "Fun-Adhesiveness-362",
        "excerpt": "Hi there!\n\n I don't see a problem with keeping the dependencies needed for an offline rebuild. That perfectly makes sense.\n\n One thing I'd change is how you identify the image used by each build. Copying the tag into a LABEL doesn't stop that tag from pointing to another image later. Keep the readable tag, but record the image digest alongside the source commit in your build records. At least that",
        "posted_at": "2026-11-06T23:52:46.000Z",
        "author_url": "https://www.reddit.com/user/Fun-Adhesiveness-362/"
      }
    ],
    "evidence": [
      "[post] As our concept is based on tags, and the docker tags are not the most reliable thing in the world, I keep also the tagged image name as a LABEL within the image.",
      "[post] At this point I ask myself if we are going in the right direction and the increased complexity in the toolchain management is because of the concept we've decided to go for",
      "[post] Note: I know that I can save the image in a registry, in parallel I'm trying to find solutions (if possible) to reduce storage costs (each image ~20GB)."
    ],
    "virality": "low",
    "post_date": "2026-11-06T19:09:25.000Z",
    "post_kind": "text",
    "post_text": "Greetings,\n\nI would like to share a problem that I'm facing with Docker, looking for some ideas.\n\nIn our company we've started to use docker hosted in an Azure DevOps cloud ubuntu machine, there we have an Azure self-hosted agent installed. We work only with firmware projects and this is our build server. We have this setup for 3 years.\n\nUsually, I generate the docker images on demand according with the project requirements.In our firmware projects hosted in git we have a yaml pipeline configuration where we set the image tag so that the proper container can be raised to process the build.\n\nWe have a requirement from safety standards (we must keep the project artifacts/infrastructure from 10 to 15 years), because of that I keep all the dependencies I need to reproduce/re-create an image as debian installers (for offline installation). I've created a script which runs prior the build process, which creates a yaml manifest containing all the image packages and include this manifest also in the image (at /etc/manifest.yaml) for runtime check. Then it's possible to verify the content via the manifest hash. Examples of dependencies we have are cmake, unit test tools, static code analyzer, and so on.We decided to keep everything in a single image because most of the tools require the compiler, so that the image complexity keeps lower as possible.\n\nAs we have different projects using...",
    "sentiment": "mixed",
    "subreddit": "docker",
    "event_date": "2026-11",
    "post_title": "Question over general docker usage/concept",
    "prominence": "core",
    "source_url": "https://www.reddit.com/r/docker/comments/1xplb98/question_over_general_docker_usageconcept/",
    "entity_role": "vendor",
    "post_author": "vaugsantos90",
    "upvote_ratio": 1,
    "mention_count": 2,
    "mention_surge": false,
    "subreddit_url": "https://www.reddit.com/r/docker/",
    "total_upvotes": 2,
    "comments_total": 11,
    "total_comments": 11,
    "event_date_text": "for 3 years",
    "other_companies": [
      {
        "name": "Azure DevOps",
        "role": "partner",
        "domain": "microsoft.com"
      },
      {
        "name": "Sonatype Nexus",
        "role": "alternative",
        "domain": "sonatype.com"
      }
    ],
    "post_author_url": "https://www.reddit.com/user/vaugsantos90/",
    "signal_category": "feedback",
    "comments_included": 5,
    "products_mentioned": [
      "Docker"
    ]
  }
}

Long text fields are shortened on this page.

Looking up one signal by its id is free. Enrich costs 2 credits per signal returned; a call with no results is free.