3,860
edits
Firefox OS/Performance/Using Docker to Ease Debugging Firefox OS: Difference between revisions
Firefox OS/Performance/Using Docker to Ease Debugging Firefox OS (view source)
Revision as of 14:00, 1 February 2015
, 1 February 2015Lakrits moved page FirefoxOS/Performance/Using Docker to Ease Debugging Firefox OS to Firefox OS/Performance/Using Docker to Ease Debugging Firefox OS: The official spelling of "Firefox OS" leaves a space between the two parts of the name. It's...
m (Lakrits moved page FirefoxOS/Performance/Using Docker to Ease Debugging Firefox OS to Firefox OS/Performance/Using Docker to Ease Debugging Firefox OS: The official spelling of "Firefox OS" leaves a space between the two parts of the name. It's...) |
|||
| (4 intermediate revisions by one other user not shown) | |||
| Line 11: | Line 11: | ||
## Create a Jenkin's task to drive the docker daemon to update code, do the build, and snapshot the docker image into the registry? | ## Create a Jenkin's task to drive the docker daemon to update code, do the build, and snapshot the docker image into the registry? | ||
## Investigate using amazon elastic beanstalk to scale docker image creation to one snapshot per commit? | ## Investigate using amazon elastic beanstalk to scale docker image creation to one snapshot per commit? | ||
== | == Identify Registry to Store Docker Images == | ||
=== Private Registry === | |||
If we go with a private registry, this process is already documented in several places: [http://www.activestate.com/blog/2014/01/deploying-your-own-private-docker-registry] [https://blog.codecentric.de/en/2014/02/docker-registry-run-private-docker-image-repository/] | |||
The only upside of a private registry is branding and the possibility of access control for private, security/prototype related debugging/patching of Firefox OS. | |||
=== Public Registry === | |||
If we store docker images in the public docker.io registry then everybody in the Firefox OS community will have access to them. This would be really helpful for getting developers up to speed in a minimum amount of time. | |||
I think for doing a docker image per commit, we should just use the public registry. | |||
== Dockerfile for a B2G Build Image == | == Dockerfile for a B2G Build Image == | ||
| Line 23: | Line 32: | ||
<pre> | <pre> | ||
from ubuntu | from ubuntu | ||
# get 4.6 gnu toolchain | |||
# get android sdk | |||
# get git, ctags, cscope, vim, emacs, and everything needed to run cleopatra web app locally. | |||
# get B2G repo | |||
</pre> | </pre> | ||