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

[Fix #59] image history, use v2 manifest instead of v1 #61

Merged
merged 7 commits into from Dec 19, 2018

Conversation

@Joxit
Copy link
Owner

commented Dec 15, 2018

A bug was found, when I browse with the browser cache, the tag history does not load because it receives a response with a docker schema v2 and it needs a v1 schema.

What I will do is to use v2 schema instead of v1 (with this, I can use DockerImage object with listeners/triggers).
Moreover, I could make queries savings by passing the DockerImage object directly.

Fixes: #59

@Joxit Joxit added the high priority label Dec 15, 2018

@Joxit Joxit self-assigned this Dec 15, 2018

@Joxit Joxit added this to To do in docker-registry-ui via automation Dec 15, 2018

Joxit added some commits Dec 15, 2018

[fix-image-history] Add config values for top level history and impro…
…ve element values rendering

Move icons to js mapping function instead of CSS
In dockerfile, author cand be randered through `MAINTAINER xxx` or `LABEL maintainer=xxx`
[fix-image-history] Create move history-elements in its own tag `tag-…
…history-element`

- Add id and ExposedPort
- Better rendering for arrays
- Add more const instead of var

@Joxit Joxit moved this from To do to In progress in docker-registry-ui Dec 17, 2018

@Joxit Joxit merged commit 03e4d6b into master Dec 19, 2018

docker-registry-ui automation moved this from In progress to Done Dec 19, 2018

@Joxit Joxit deleted the fix/image-history branch Dec 19, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
1 participant
You can’t perform that action at this time.