Activity
From 06/03/2016 to 07/02/2016
06/28/2016
-
09:33 AM Revision 692e3a26 (foreman_docker): Fixes #15528 - 'command' should not be required
-
06:02 AM Bug #15528 (Closed): "new container" should not require command to be specified
- Applied in changeset commit:foreman-docker|692e3a2621d65e0ef3a8cbf928b8d43919d70d3e.
-
03:49 AM Bug #15528 (Ready For Testing): "new container" should not require command to be specified
- 06:01 AM Revision 79b587b5 (foreman-docker): Merge branch 'master' of https://github.com/theforeman/foreman-docker
-
05:33 AM Revision 692e3a26 (foreman-docker): Fixes #15528 - 'command' should not be required
06/27/2016
-
05:35 PM Bug #15528 (Closed): "new container" should not require command to be specified
- Many images have CMD or ENTRYPOINT already present in Dockerfile so the "Command" field should not be required.
06/23/2016
-
12:44 PM Revision b2f2c848 (foreman_docker): Refs #14570 - Destroy Container db object
- When deleting with container uuid params, the container object should be destroyed as well
- 09:01 AM Revision 61b631bb (foreman-docker): Merge branch 'master' of https://github.com/theforeman/foreman-docker
-
08:44 AM Revision b2f2c848 (foreman-docker): Refs #14570 - Destroy Container db object
- When deleting with container uuid params, the container object should be destroyed as well
06/21/2016
-
09:39 AM Bug #14570 (Ready For Testing): after container deletion the container name cannot be reused
-
07:32 AM Bug #14570 (Assigned): after container deletion the container name cannot be reused
- Provided solutions (PRs) do not completely solve the issue.
please check with Rails console, deleted Container (the ...
Also available in: Atom