Activity
From 11/12/2015 to 12/11/2015
12/11/2015
- 12:37 PM Bug #12785 (Ready For Testing): Raise foreman min version to 1.11 as it becomes Rails 4 compatible
- 12:35 PM Bug #12785 (Closed): Raise foreman min version to 1.11 as it becomes Rails 4 compatible
- 09:32 AM Bug #12781 (New): when there is an error creating container, processing it tries to access 'full_messages'
- ...
- 04:22 AM Bug #12779 (New): Docker plugin installation
- Ive tried to install both way's through the foreman-installer and also by apt-get but i didn't see the plugin in by ...
12/08/2015
- 07:01 AM Bug #12726 (Closed): Add missing attr_accessible to models
- Applied in changeset commit:foreman-docker|79287e76f65f65440adcdee290e940f0f6e70371.
12/07/2015
12/03/2015
- 01:02 PM Bug #12681 (Closed): Support rubocop 0.35.1
- Applied in changeset commit:foreman-docker|7ff105d1beec02c6dfbbd599dd8acf1a73d02f62.
- 04:59 AM Bug #12681 (Ready For Testing): Support rubocop 0.35.1
- 04:57 AM Bug #12681 (Closed): Support rubocop 0.35.1
11/25/2015
- 11:23 PM Bug #12608 (New): undefined method `cpu_shares'
- Description of problem:
When creating new container the container is started though the below message is displayed.
... - 03:42 AM Bug #12600: Name clash with foreman_deployments in production env
- I don't think this is a problem with the foreman_docker plugin, https://github.com/theforeman/foreman_deployments/blo...
- 03:41 AM Bug #12600 (Ready For Testing): Name clash with foreman_deployments in production env
- 03:38 AM Bug #12600 (Ready For Testing): Name clash with foreman_deployments in production env
- When foreman_deployments plugin is added to a Foreman instance with foreman_docker in a production environment, the s...
Also available in: Atom