Bug 9555

Summary:	Create Toaster Docker container
Product:	[Build System, Metadata & Runtime] Toaster	Reporter:	Belen Barros Pena <belen.barros.pena>
Component:	toaster	Assignee:	Randy Witt <randy.e.witt>
Status:	RESOLVED FIXED	QA Contact:	Libertad <libertad.gonzalez.de.la.cruz>
Severity:	normal
Priority:	Medium+	CC:	belen.barros.pena, brian.avery, jessica.zhang, stanciux.mihail
Version:	unspecified
Target Milestone:	2.2 M2
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	Yes (doc changes required)
Bug Depends on:
Bug Blocks:	9586, 9617

Description Belen Barros Pena 2016-04-28 13:36:04 UTC

The purpose of creating a Toaster Docker container is twofold:

1) It will simplify the task of setting a "production" instance of Toaster (http://www.yoctoproject.org/docs/latest/toaster-manual/toaster-manual.html#toaster-setting-up-a-production-instance-of-toaster), something we know trips people up

2) Could replace the existing Build Appliance as the offered mechanism to try Yocto Project.

Comment 1 Randy Witt 2016-07-12 18:22:57 UTC

This is done and available, but the container isn't being built using oe-core. https://github.com/crops/toaster-container

If it is desired that it be built using oe-core then this is blocked by 9502.

Comment 2 brian avery 2016-07-12 20:31:25 UTC

My preference is that we go with a standard distro solution for the moment.  This has a couple of advantages:
1) it is a shorter path forward
2) since this is all pretty new, if a user need to exec into the contsiner to do something special, the apt-get mechanism available in the standard distro container makes it easy.
3) We can use a cron job to keep the containers up to date.

The future:

1) We would like to use the webhook Bug 9922 to keep the containers up to date.
2) we would like to be able to use YP to make an oe-core minimal container for our applications.  This would have a lot of size and reproducibility advantages: Bug 9502

Comment 3 Randy Witt 2016-07-19 18:03:20 UTC

This currently exists at https://github.com/crops/toaster-container.

Since virtualenv no longer works with bitbake, I'm updating the container and adding some testing.

Comment 4 Randy Witt 2016-08-10 21:55:09 UTC

This is finished and currently exists on dockerhub. There are three repos on dockerhub:

https://hub.docker.com/r/crops/toaster-krogoth/
https://hub.docker.com/r/crops/toaster-master/
https://hub.docker.com/r/crops/toaster

The "crops/toaster" repo is "floating" and corresponds to the last release, currently "krogoth".

"crops/toaster-master" contains master builds and toaster-next.

The container images are built, tested and pushed to dockerhub whenever the master, krogoth or toaster-next branches change.

https://travis-ci.org/crops/toaster-container