Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Image Request]: .NET runtime-deps variant #423

Open
patflynn opened this issue Apr 5, 2023 · 5 comments
Open

[Image Request]: .NET runtime-deps variant #423

patflynn opened this issue Apr 5, 2023 · 5 comments
Labels
image-request tag for new chainguard image requests

Comments

@patflynn
Copy link
Contributor

patflynn commented Apr 5, 2023

What software would you like us to add to our image catalog? (one per issue please)

See comment here.

which versions of the containerized software do you need?

we should do it for all versions that support this variant

Add some justification for why this specific image and versions are important.

smaller is better
@patflynn patflynn added needs-triage applied to all new customer/user issues. Removed after triage occurs. image-request tag for new chainguard image requests labels Apr 5, 2023
@patflynn patflynn mentioned this issue Apr 5, 2023
Closed
@amouat amouat removed their assignment Apr 14, 2023
@patflynn patflynn removed the needs-triage applied to all new customer/user issues. Removed after triage occurs. label Apr 21, 2023
@patflynn
Copy link
Contributor Author

patflynn commented May 9, 2023

this was done https://github.com/chainguard-images/images/tree/main/images/dotnet-runtime

@patflynn patflynn closed this as completed May 9, 2023
@gareth-houghton
Copy link

Hey @patflynn,

The dotnet-runtime image isn't the same as runtime-deps, .net really doesn't make things clear around this. You can build any .net app so that it doesn't require a dotnet runtime to be installed, but you do need a few packages, this is the rationale for the runtime-deps image.

I had a quick look at the off the shelf runtime-deps image and it looks like the alpine flavour has these dependencies:

  • krb5-libs
  • libgcc
  • libintl
  • libssl3
  • libstdc++
  • zlib

I managed to find the same list in the Microsoft docs too so at least they're consistent!

@patflynn
Copy link
Contributor Author

Oh I see. This sounds a little like graalvm.

@patflynn patflynn reopened this May 12, 2023
@patflynn
Copy link
Contributor Author

@gareth-houghton Not sure when we'll get to this but feel free to send a PR! This one sounds straight forward. Sounds like the test will need a .net app compiled to run in a runtime-deps environment.

@gareth-houghton
Copy link

@patflynn No problem, I totally understand the lack of priority given that there's already .net images and this is a nice to have. I've got plenty of sample apps that I can test with, so let me see if I can find some time and see about getting a PR up for it - I've not done much with apko yet so might be slow progress!

developer-guy pushed a commit to Dentrax/images that referenced this issue Feb 12, 2024
@mritunjaysharma394
adds aws-for-fluent-bit with fluent-bit 1.9 (chainguard-images#423)
69c3871 
Signed-off-by: Mritunjay <mritunjay.sharma@chainguard.dev>
@xnox xnox mentioned this issue May 16, 2024
Merged
xnox added a commit to xnox/images that referenced this issue May 16, 2024
@xnox
github: upgrade chainguard-dev actions commit
df5268b 
This brings in the following changes:

ba1a9c9 (HEAD -> main, upstream/main, upstream/HEAD) update action to use new c>
77965ce Bump tj-actions/changed-files from 44.3.0 to 44.4.0 (chainguard-images#429)
25a26c8 upgrade arifact actions to v4 (chainguard-images#432)
b71790d update ci tests (chainguard-images#431)
4a4a027 bump kind to v0.23.0 add 1.30 k8s / remove 1.23/24 and updates kindest/>
3d3cb8d Bump step-security/harden-runner from 2.7.0 to 2.7.1 (chainguard-images#425)
73d51cb Bump actions/setup-go from 5.0.0 to 5.0.1 in /boilerplate (chainguard-images#426)
1105f78 Bump actions/setup-go from 5.0.0 to 5.0.1 (chainguard-images#427)
67c8811 Bump actions/checkout from 4.1.3 to 4.1.5 (chainguard-images#428)
97bd985 deprecate setup-chainctl in favor of the other repo (chainguard-images#399)
8799517 Bump actions/upload-artifact from 4.3.2 to 4.3.3 in /kind-diag (chainguard-images#422)
4995b58 Update README.md (chainguard-images#423)
bcf69bc Bump actions/upload-artifact from 4.3.1 to 4.3.2 in /kind-diag (chainguard-images#419)
7576b91 Bump tj-actions/changed-files from 44.0.1 to 44.3.0 (chainguard-images#420)
9bad65a Bump actions/checkout from 4.1.2 to 4.1.3 (chainguard-images#421)
270ade7 Bump tj-actions/changed-files from 44.0.0 to 44.0.1 (chainguard-images#415)
2cadca1 Bump actions/checkout from 4.1.1 to 4.1.2 (chainguard-images#406)
4f1d9b7 Bump reviewdog/action-setup from 1.2.1 to 1.3.0 in /boilerplate (chainguard-images#405)
d052d8b Bump reviewdog/action-setup from 1.2.1 to 1.3.0 in /donotsubmit (chainguard-images#407)
0e99253 Don't triple-wrap logs, just upload as zip (chainguard-images#410)
48e6493 Bump tj-actions/changed-files from 43.0.1 to 44.0.0 (chainguard-images#413)
7071df0 update changed-files (chainguard-images#412)

Given there are no releases of chainguard-dev actions, and bots do not
bump commit ids, maybe we should switch back to tracking @main like we
used to.

Signed-off-by: Dimitri John Ledkov <dimitri.ledkov@chainguard.dev>
k4leung4 pushed a commit that referenced this issue May 21, 2024
@xnox
github: upgrade chainguard-dev actions commit (#2695)
dba80bc 
This brings in the following changes:

ba1a9c9 (HEAD -> main, upstream/main, upstream/HEAD) update action to use new c>
77965ce Bump tj-actions/changed-files from 44.3.0 to 44.4.0 (#429)
25a26c8 upgrade arifact actions to v4 (#432)
b71790d update ci tests (#431)
4a4a027 bump kind to v0.23.0 add 1.30 k8s / remove 1.23/24 and updates kindest/>
3d3cb8d Bump step-security/harden-runner from 2.7.0 to 2.7.1 (#425)
73d51cb Bump actions/setup-go from 5.0.0 to 5.0.1 in /boilerplate (#426)
1105f78 Bump actions/setup-go from 5.0.0 to 5.0.1 (#427)
67c8811 Bump actions/checkout from 4.1.3 to 4.1.5 (#428)
97bd985 deprecate setup-chainctl in favor of the other repo (#399)
8799517 Bump actions/upload-artifact from 4.3.2 to 4.3.3 in /kind-diag (#422)
4995b58 Update README.md (#423)
bcf69bc Bump actions/upload-artifact from 4.3.1 to 4.3.2 in /kind-diag (#419)
7576b91 Bump tj-actions/changed-files from 44.0.1 to 44.3.0 (#420)
9bad65a Bump actions/checkout from 4.1.2 to 4.1.3 (#421)
270ade7 Bump tj-actions/changed-files from 44.0.0 to 44.0.1 (#415)
2cadca1 Bump actions/checkout from 4.1.1 to 4.1.2 (#406)
4f1d9b7 Bump reviewdog/action-setup from 1.2.1 to 1.3.0 in /boilerplate (#405)
d052d8b Bump reviewdog/action-setup from 1.2.1 to 1.3.0 in /donotsubmit (#407)
0e99253 Don't triple-wrap logs, just upload as zip (#410)
48e6493 Bump tj-actions/changed-files from 43.0.1 to 44.0.0 (#413)
7071df0 update changed-files (#412)

Given there are no releases of chainguard-dev actions, and bots do not
bump commit ids, maybe we should switch back to tracking @main like we
used to.

Signed-off-by: Dimitri John Ledkov <dimitri.ledkov@chainguard.dev>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
image-request tag for new chainguard image requests
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@amouat @patflynn @gareth-houghton