Put your Dockerfile, accompanying configuration files, and control scripts somewhere on the Internet where it can be directly downloaded (just HTTP(s), no registration pages or special download methods, please). If you have no access at all and would like space, please visit The sponsors ticket system, log in, and file a ticket with component "Initial package hosting request". You will be given access to Fedorapeople.

Fill out a request for review in bugzilla. Summary field needs to be in format of Container Review Request:... If the : is omitted the fedpkg tool’s request-repo will error out.

If you do not have any package or container layered image already in Fedora, this means you need a sponsor and to add FE-NEEDSPONSOR (Bugzilla id:177841) to the bugs being blocked by your review request. For more information read the How to Get Sponsored into the Packager Group page.

Wait for someone to review your Dockerfile! At this point in the process, the '''fedora-review flag''' is blank, meaning that no reviewer is assigned.

There may be comments from people that are not formally reviewing the package, they may add NotReady to the Whiteboard field, indication that the review request is not yet ready, because of some issues they report. After you have addressed them, please post the URLs to the updated Dockerfile and associated files and remove it from the Whiteboard. It is expected that you will respond to commentary, including updating your submission to address it; if you do not, your ticket will be closed.

A reviewer takes on the task of reviewing your package. They will set the '''fedora-review flag''' to '''?'''

The reviewer will review your Dockerfile. You should fix any blockers that the reviewer identifies. Once the reviewer is happy with the package, the '''fedora-review''' flag will be set to '''+''', indicating that the package has passed review.

At this point, you need to make an SCM admin request for your newly approved Layered Image. If you have not yet been sponsored, you will not be able to progress past this point. (You will need to make sure to request the container namespace in src.fedorproject.org)

Checkout the package using "fedpkg clone container/<container-name>" do a final check of Dockerfile, etc.

When this is complete, you can add relevant container files into the SCM. Required files should be:

Dockerfile

help.md file

Request a build by running "fedpkg container-build".

Repeat the process for other branches you may have requested. (NOTE: The FROM line in the Dockerfile for each branch will need to reflect which Fedora release distgit branch it is in or else the builds will collide in koji)

You should make sure the review ticket is closed. You are welcome to close it once the Container Layered Image has been built on the requested branches, or if you built for one of the Fedora release branches you can ask Bodhi to close the ticket for you when it completes the process. If you close the ticket yourself, use '''NEXTRELEASE''' as the resolution.

Go through the MUST items listed in Container Guidelines.

Go through the SHOULD items in Container Guidelines.

Include the text of your review in a comment in the ticket. For easy readability, simply use a regular comment instead of an attachment.

Take one of the following actions:

'''ACCEPT''' - If the container layered image is good, set the '''fedora-review''' flag to '''+'''

'''FAIL, LEGAL''' - If the container layered image is legally risky for whatever reason (known patent or copyright infringement, trademark concerns) close the bug WONTFIX and leave an appropriate comment (i.e. we don’t ship mp3). Set the '''fedora-review''' flag to '''-''', and have the review ticket block FE-Legal.

'''FAIL, OTHER''' - If the container layered image is just way off or unsuitable for some other reason, and there is no simple fix, then close the bug WONTFIX and leave an appropriate comment (i.e. we don’t package pornography for redistribution, sorry. Or, this isn’t a specfile, it’s a McDonald’s menu, sorry.) Set the '''fedora-review''' flag to '''-'''.

'''NEEDSWORK''' - Anything that isn’t explicitly failed should be left open while the submitter and reviewer work together to fix any potential issues. Mark the bug as NEEDINFO while waiting for the reviewer to respond to improvement requests; this makes it easier for reviewers to find open reviews which require their input.

Once a package is flagged as '''fedora-review +''' (or '''-'''), the Reviewer’s job is done although they may be called upon to assist the Contributor with the import/build/update process and to ensure that the Contributor closes the ticket out when the process is complete.