github-starred/awesome-compose
2
0
Fork 0
mirror of https://github.com/docker/awesome-compose.git synced 2026-03-09 06:52:08 -05:00
Code Issues 627 Packages Projects Releases Wiki Activity

[PR #300] Pin Docker base image in flask/app/Dockerfile #969

New Issue
Open
opened 2026-03-07 21:27:44 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-03-07 21:27:44 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/docker/awesome-compose/pull/300
Author: @atomist[bot]
Created: 10/7/2022
Status: 🔄 Open

Base: master ← Head: atomist/pin-docker-base-image/flask/app/dockerfile

📝 Commits (1)

  • 2dd28f4 Pin Docker image python:3.10-alpine

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 flask/app/Dockerfile (+1 -1)

📄 Description

This pull request pins the Docker base image python:3.10-alpine in flask/app/Dockerfile to the current digest.

2dd28f4319/flask/app/Dockerfile (L2-L2)

Digest sha256:c9d3c11e89887c82efeb4f4fee8771a406cf42f41aebbd23148906d5fe3c1426 references a multi-CPU architecture image manifest. This image supports the following architectures:

Pinning FROM lines to digests makes your builds repeatable. Atomist will raise new pull requests whenever the tag moves, so that you know when the base image has been updated. You can follow a new tag at any time. Just replace the digest with the new tag you want to follow. Atomist, will switch to following this new tag.

File changed:

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/docker/awesome-compose/pull/300 **Author:** [@atomist[bot]](https://github.com/apps/atomist) **Created:** 10/7/2022 **Status:** 🔄 Open **Base:** `master` ← **Head:** `atomist/pin-docker-base-image/flask/app/dockerfile` --- ### 📝 Commits (1) - [`2dd28f4`](https://github.com/docker/awesome-compose/commit/2dd28f43199fc83ffcc544065022f81696571873) Pin Docker image python:3.10-alpine ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `flask/app/Dockerfile` (+1 -1) </details> ### 📄 Description This pull request pins the Docker base image `python:3.10-alpine` in [`flask/app/Dockerfile`](https://github.com/docker/awesome-compose/blob/2dd28f43199fc83ffcc544065022f81696571873/flask/app/Dockerfile) to the current digest. https://github.com/docker/awesome-compose/blob/2dd28f43199fc83ffcc544065022f81696571873/flask/app/Dockerfile#L2-L2 <!-- atomist:hide --> Digest `sha256:c9d3c11e89887c82efeb4f4fee8771a406cf42f41aebbd23148906d5fe3c1426` references a [multi-CPU architecture image manifest](https://docs.docker.com/desktop/multi-arch/). This image supports the following architectures: * [<code>sha256:35af7f3c70f011dce12160f8402b3d86669488c53e160fe56a34ff245685eae1</code>](https://hub.docker.com/layers/python/library/python/3.10-alpine/images/sha256-35af7f3c70f011dce12160f8402b3d86669488c53e160fe56a34ff245685eae1) <code>linux/ppc64le</code> <!-- atomist:show --> --- <!-- atomist:hide --> Pinning `FROM` lines to digests makes your builds repeatable. Atomist will raise new pull requests whenever the tag moves, so that you know when the base image has been updated. You can follow a new tag at any time. Just replace the digest with the new tag you want to follow. Atomist, will switch to following this new tag. <!-- atomist:show --> --- File changed: - [`flask/app/Dockerfile`](https://github.com/docker/awesome-compose/blob/atomist/pin-docker-base-image/flask/app/dockerfile/flask/app/Dockerfile) <!-- atomist:hide --> <!-- atomist:show --> <!-- [atomist:generated] [atomist-skill:atomist/docker-base-image-policy] [atomist-version:0.1.109] [atomist-configuration:policy-cfg] [atomist-workspace-id:AR5C23OPM] [atomist-tx:3465630] [atomist-correlation-id:ac094729-5a48-438a-a70b-834af79c15e2.aOIMYV48nkBjVMvdMwYgw] [atomist-diff:6f7d42f593a560802210b209363325be9e62752f0cc271220ee3ecd470910547] --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-03-07 21:27:44 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
good first issue
proposal
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-compose#969
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?