Dear relentless RIOTers,
I would like to introduce an official repository for keeping Dockerfiles used for building Docker images. The images can be used to build RIOT in conjunction with the work being proposed in 1. The images will contain supported versions of tool chains to make getting started with RIOT more convenient. I volunteer as maintainer for the Dockerfile repository and the pre-built images which will be published at the Docker hub 2. The reason for making a separate repository instead of using /dist/XXXXX is that we can more easily keep track of tool chain updates, and we can use the Docker hub automatic build feature to automatically update the images. Using the core RIOT code repo for Dockerfiles will cause an unnecessary amount of rebuilds when watching it with the automatic build feature of the Docker hub.
Also, I need to have an organisation owner (Oleg, Kaspar, Emmanuel or
Matthias Wählisch) create the repo since maintainers do not have the
proper access to do it.
I don't have any particular ideas for the name, so, for me "riotbuild" (or
"riotdocker") would be fine.
Also, I need to have an organisation owner (Oleg, Kaspar, Emmanuel or
Matthias Wählisch) create the repo since maintainers do not have the proper
access to do it.
Sure, I can do so. Let's wait if no one objects against the proposed name.
> Also, I need to have an organisation owner (Oleg, Kaspar, Emmanuel or
> Matthias Wählisch) create the repo since maintainers do not have the proper
> access to do it.
Sure, I can do so. Let's wait if no one objects against the proposed name.
This somehow disappeared from my radar. I think you need to give me admin
access to the repository in order to move it to the RIOT organization (and
rename it to riotdocker).
> Also, I need to have an organisation owner (Oleg, Kaspar, Emmanuel or
> Matthias Wählisch) create the repo since maintainers do not have the proper
> access to do it.
Sure, I can do so. Let's wait if no one objects against the proposed name.
This somehow disappeared from my radar. I think you need to give me admin
access to the repository in order to move it to the RIOT organization (and
rename it to riotdocker).
What do you mean?
If you create a new empty riotdocker repo in the RIOT organization we
can push the Dockerfile commits to it.
> This somehow disappeared from my radar. I think you need to give me admin
> access to the repository in order to move it to the RIOT organization (and
> rename it to riotdocker).
What do you mean?
If you create a new empty riotdocker repo in the RIOT organization we
can push the Dockerfile commits to it.
Yes, of course that's possible. I thought it might be easier to move the
already existing repository to the RIOT-OS organization, but anyway here we
go:
I have now added it under the name riot/riotbuild
Docker (I figured the
docker suffix on a Docker hub repo is kind of redundant)
Great!
It needs further configuration on the GitHub side by an administrator,
follow the instructions on this page for the RIOT/riotdocker
repository:
Set up Automated Builds | Docker Docs
Ok, I'll do that.
Oleg: Do you have a docker hub account? I can add you as an
administrator to the riot organization.