Skip to content

Info on hub.docker.com still outdated #20

Description

@Tekki

My comment in #15 didn't get noticed, I open a new issue.
Your repo on Docker Hub is not an automated build, you have to update the README manually.
Here you find more infos about automated builds. Seems it isn't possible to convert an existing repo, there is an open issue on Docker: docker/hub-feedback#794

I don't want to be the one who always complains, so I'll propose some changes to the README.

Activity

  1. zakame commented on Nov 18, 2018

    @zakame
    Contributor

    Sounds like one needs to create a PR updating https://github.com/docker-library/docs/tree/master/rakudo-star

    This can be semi-automated via adding an update.sh in this repo and letting @docker-library-bot commit here, cf Perl/docker-perl#24 (comment)

  2. Tekki commented on Apr 13, 2019

    @Tekki
    ContributorAuthor

    Now that 2019.03 is on Dockerhub, why is the README still not updated?

  3. tianon commented on Jun 1, 2019

    @tianon
    Contributor

    That'd be because nobody has made a PR to https://github.com/docker-library/docs/tree/master/rakudo-star 😄

    To be clear, giving @docker-library-bot commit bits here would not do anything with README.md -- the format in https://github.com/docker-library/docs/tree/master/rakudo-star is different (and templated so that all official images have a consistent image description format).

    The approach we take with images maintained under https://github.com/docker-library is to make the README.md inside the repository just a stub that points to Docker Hub as the canonical source (see https://github.com/docker-library/golang#readme, for example), which helps us avoid duplicated documentation effort.

    Some other images prefer to keep the documentation on Docker Hub explicitly slim and link elsewhere for documentation (either to a markdown file in GitHub or better yet to actual upstream documentation content so the documentation for the image lives within the proper upstream documentation directly).

  4. JJ commented on Jun 2, 2019

    @JJ
    Contributor
  5. Tekki commented on Jun 2, 2019

    @Tekki
    ContributorAuthor

    I have permission, and it's not required. But I think that an official maintainer has to make this PR.

  6. tianon commented on Jun 3, 2019

    @tianon
    Contributor

    It doesn't require any permissions of any kind -- we just need someone to take a look at https://github.com/docker-library/docs/blob/master/rakudo-star/content.md and provide a PR to that repository updating it as desired (which we then typically ask one of the image maintainers to sign-off on whether they approve of the changes).

  7. JJ commented on Feb 11, 2020

    @JJ
    Contributor

    Even more outdated now...

  8. moritz commented on Apr 29, 2020

    @moritz
    Member
  9. moritz commented on Apr 30, 2020

    @moritz
    Member

    I've updated the info that I could find how to update. If stuff's still wrong, please open a merge request against docker-library/docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions