63c9218175
* Add repo metadata, start with categories! scripts for checking repo categories, updating the canonical set added categories to push.pl * Add initial set of semi-acurate categories * Adjustments following tianon's review * Simplify metadata.sh use cases (CI or interactive); just diff and check all the time Update README.md about metadata.sh usage * Unify the categories checks into one jq expressions * Update initial categories * Link to Docker docs for categories; minor categories script adjustments |
||
|---|---|---|
| .. | ||
| README-short.txt | ||
| README.md | ||
| content.md | ||
| github-repo | ||
| license.md | ||
| logo.png | ||
| maintainer.md | ||
| metadata.json | ||
README.md
Quick reference
-
Maintained by:
the Docker Community -
Where to get help:
the Docker Community Slack, Server Fault, Unix & Linux, or Stack Overflow
Supported tags and respective Dockerfile links
Quick reference (cont.)
-
Where to file issues:
https://github.com/tianon/docker-brew-cirros/issues -
Supported architectures: (more info)
amd64,arm32v7,arm64v8,ppc64le -
Published image artifact details:
repo-info repo'srepos/cirros/directory (history)
(image metadata, transfer size, etc) -
Image updates:
official-images repo'slibrary/cirroslabel
official-images repo'slibrary/cirrosfile (history) -
Source of this description:
docs repo'scirros/directory (history)
What is CirrOS?
The CirrOS project provides linux disk and kernel/initramfs images. The images are well suited for testing as they are small and boot quickly. Please note that:
- Images are provided for test only. They should not be used in production.
- Images have well known login information. Users can log in with 'cirros:letsgocubs' locally or remotely and have passwordless sudo access to root.
CirrOS images have useful tools and function for debugging or developing cloud infrastructure.
License
View license information for the software contained in this image:
The code for building CirrOS is available under GPLv2. The binary images that will be distributed contain many different licenses all of which are opensource.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in the repo-info repository's cirros/ directory.
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.