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.

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

inline images: media-types.png is inline #73

Merged
merged 1 commit into from
May 23, 2016
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions Makefile
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,7 @@ DOC_FILES := \
code-of-conduct.md \
project.md \
media-types.md \
inline-png-media-types.md \
manifest.md \
serialization.md

Expand Down Expand Up @@ -70,11 +71,12 @@ lint:
test:
go test -race ./...

media-types.png: media-types.dot

%.png: %.dot
dot -Tpng $^ > $@

inline-png-%.md: %.png
@printf '<img src="data:image/png;base64,%s" alt="$*"/>\n' "$(shell base64 $^)" > $@

.PHONY: \
validate-examples \
oci-image-tool \
Expand Down
2 changes: 0 additions & 2 deletions media-types.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,4 @@ This section shows where the OCI Image Specification is compatible with formats

The following figure shows how the above media types reference each other:

![Media Types](media-types.png)

A reference is defined as the target content digest, as defined by the [Registry V2 HTTP API Specificiation](https://docs.docker.com/registry/spec/api/#digest-parameter). The manifest list being a "fat manifest" references one or more image manifests per target platform. An image manifest references exactly one target configuration and possibly many layers.