Home

Welcome to the Dockerfiles project wiki!

Find the platform, OS and image of your needs. Copy and integrate it into your own project. The Dockerfiles project helps you build and use Open Visual Cloud software stack. The project targets multiple dominant use cases and provides base dockerfiles, which you can build into the corresponding docker images.

If for some reason, dockers are not part of your project ingredients, the project can be a reference if you need to build software stacks such as FFmpeg and GStreamer during bare metal installation.

Release

• v23.06 - Jun 20 2023
• v23.1 - Mar 10 2023
• v22.3 - Mar 4 2022
• v21.6.1 - Aug 9 2021
• v21.6 - July 22 2021
• v21.3.1 - May 17 2021
• v21.3 - Mar 24 2021
• v20.10 - Nov 4 2020
• v20.7 - Aug 13 2020
• v20.4 - May 11 2020
• v20.3.1 - Mar 10 2020
• v20.3 - Mar 06 2020
• v20.2 - Feb 09 2020
• v20.1 - Jan 11 2020
• older releases

Note: From Oct year 2019, the release version followes the convention: Year.Month.MinorVersion

How to Contribute

We welcome community contributions to the Open Visual Cloud Dockerfiles repository. If you have an idea how to improve the product, please share it with us doing the following steps:

• Make sure you can build the product and run tests with your patch
• In case of a larger feature, provide a relevant unit tests on https://github.com/OpenVisualCloud/Dockerfiles/tree/master/test
• Submit a pull request at https://github.com/OpenVisualCloud/Dockerfiles/pulls We will review your contribution and, if any additional fixes or modifications are necessary, may give some feedback to guide you. When accepted, your pull request will be merged into GitHub* repositories.

Open Visual Cloud Dockerfiles is licensed under BSD 3-Clause "New" or "Revised" License. By contributing to the project, you agree to the license and copyright terms therein and release your contribution under these terms.

Release Process

1. Create release branch from Master to support preparation of a new production release, i.e. regression test, bug fix before a release.
2. Release branch only allows for minor bug fixes and preparing meta-data for a release. Master is still kept on open for community development during a release cycle. Bug fixes on release branch should be merged into Master.
3. Once passed full test and approved the release, tag the release.

• Goto releases
• Click ‘Draft a new release’
• Enter the version
• Select the correct branch
• Set the release title
• Update release notes - new features, bug fixes, known issues etc.

4. Update Wiki Page for release announcement.

Support

Pls. report issue to Github Issues

More Container Solutions:

Explore more container solutions on the Intel® oneContainer Portal.