add READMEs
All checks were successful
/ build (push) Successful in 6m6s

This commit is contained in:
thislight 2024-07-14 18:12:57 +08:00
parent e5eacc25dd
commit c478804d89
No known key found for this signature in database
GPG key ID: A50F9451AC56A63E
3 changed files with 184 additions and 0 deletions

View file

@ -0,0 +1,24 @@
# Action-ready Container Images
These images is cached on action runner machines and is able to run most of the actions.
| Name | OS and Distro | Description | Note |
| - | - | - | - |
| `fedora:40` | Fedora 40 | [Description](./fedora-40/README.md) | |
| `fedora-minimal:40` | Fedora 40 | [Description](./fedora-40-minimal/README.md) | |
## FAQ
### Can I see those images as alternatives of GitHub's [actions/runner-images]?
Yes, mostly. We are working on catching up the software list on their repo, and many tools are already included in our images, but be attention that we took a different approach to install softwares (at least for now).
### Can all GitHub Actions or Forgejo Actions can be run on those images?
Well, not quite. Those images are "action-ready" because bunch of tools used by actions, like NodeJS, are preinstalled in the image. It depends on the action to support the tools and the distro.
### What's the difference between the `-minimal` version and the without?
The minimal versions are configured with only basic toolset to run the actions. The images without `-minimal` include more tools to be used directly for end users.
The minimal versions is only recommended for building custom images. They are smaller and configured the container environment. In fact, the regular versions are composed from the minimal versions.

View file

@ -0,0 +1,64 @@
# fedora-minimal:40
```yaml
container:
image: code.lightstands.xyz/standcoded/fedora-minimal:40
```
## Included Softwares
### General
- coreutils
- bash
- aria2
- jq
- yq
- zstd
- brotil
- sqlite
### Version Control
- git
- git-lfs
- git-ftp
### Container Management
- podman
- buildah
- fuse-overlayfs
### NodeJS
- nodejs
- nodejs-npm
### Python
- python3
- python3-devel
- python3-pip
- pipx
### Perl
- perl
- perl-CPAN
### Ruby
- ruby
- rubygems
### C
- clang
- gcc
## Additional Configuration
### Building Container Images
This images configured buildah to be correctly run under a container. You can use [The workflow of this project](./.forgejo/workflows/build-fedora-40.yml) as an example.

96
fedora-40/README.md Normal file
View file

@ -0,0 +1,96 @@
# fedora:40
```yaml
container:
image: code.lightstands.xyz/standcoded/fedora:40
```
## Included Softwares
### General
- coreutils
- bash
- aria2
- jq
- yq
- zstd
- brotil
- sqlite
- sqlite-devel
- binutils
### Version Control
- git
- git-lfs
- git-ftp
### Container Management
- podman
- buildah
- fuse-overlayfs
- qemu-user-static
- qemu-user-binfmt
### NodeJS
- nodejs
- nodejs-npm
- nodejs-devel
### Python
- python3-devel
- python3-pip
- pipx
- poetry
### Perl
- perl
- perl-CPAN
- perl-devel
### Ruby
- ruby
- rubygems
- ruby-devel
### C
- clang
- gcc
- bison
- flex
- "C Development Tools and Libraries"
### PHP
- php
- php-devel
- composer
### Java
| Version | Packages |
| - | - |
| 1.8.0 | java-1.8.0-openjdk, java-1.8.0-openjdk-devel |
| 11 | java-11-openjdk, java-11-openjdk-devel |
| 17 | java-17-openjdk, java-17-openjdk-devel |
| 21 | java-21-openjdk, java-21-openjdk-devel |
## Additional Configuration
### Building Container Images
This images configured buildah to be correctly run under a container. You can use [The workflow of this project](./.forgejo/workflows/build-fedora-40.yml) as an example.