We currently have Docker containers without autostart functionality.
A systemd unit could be created to start and stop them, with Docker service as dependency.
Fixes T467.
Details
Details
- Reviewers
dereckson - Maniphest Tasks
- T467: Create a systemd unit to start relevant docker containers
- Commits
- rOPS57469318129a: Systemd unit to start and stop Docker containers
Test the units on Dwellers.
Diff Detail
Diff Detail
- Repository
- rOPS Nasqueron Operations
- Lint
No Lint Coverage - Unit
No Test Coverage - Branch
- arcpatch-D20
- Build Status
Buildable 159 Build 159: arc lint + arc unit
Event Timeline
Comment Actions
Let's try to be compliant with "docker-containers" name: docker-containers-start, docker-containers-stop ?
| scripts/paas/docker/systemd/docker-containers.service | ||
|---|---|---|
| 4 ↗ | (On Diff #44) | We should put both scripts at the same place, for example at /usr/local/bin/ |
| paas/docker/systemd/docker-containers.service | ||
|---|---|---|
| 4 ↗ | (On Diff #46) | We can put them both in the same directory. If it's not Systemd specific (if we could outside of Systemd run these scripts), maybe the ideal place is /usr/local/bin? Any person in the docker group could control docker, so sbin isn't the ideal I imagine. |
| paas/docker/systemd/docker-containers.service | ||
|---|---|---|
| 4 ↗ | (On Diff #56) | Actually, systemd requires absolute path, not relative paths. Jul 15 12:30:20 dwellers.nasqueron.org systemd[1]: [/usr/lib/systemd/system/docker-containers.service:4] Executable path is not absolute, ignoring: ...er_start Let's try this:
|
Comment Actions
This doesn't match our current set of containers launched:
$ docker ps | grep -v arcanist CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 4c98054578d3 jenkinsci/jenkins "/bin/tini -- /usr/lo" 5 days ago Up 5 days 0.0.0.0:50000->50000/tcp, 0.0.0.0:38080->8080/tcp ci fd356b7b01e9 nasqueron/rabbitmq "/docker-entrypoint.s" 3 weeks ago Up 2 weeks 0.0.0.0:1883->1883/tcp, 0.0.0.0:4369->4369/tcp, 0.0.0.0:5672->5672/tcp, 0.0.0.0:8883->8883/tcp, 0.0.0.0:15672->15672/tcp, 0.0.0.0:15674->15674/tcp, 0.0.0.0:25672->25672/tcp, 0.0.0.0:61613->61613/tcp, 5671/tcp white-rabbit ff7fc9e99559 nasqueron/cachet "/usr/local/sbin/init" 3 weeks ago Up 3 weeks 443/tcp, 0.0.0.0:39080->80/tcp cachet e6add030d18c local_discourse/forum "/sbin/boot" 4 weeks ago Up 4 weeks 0.0.0.0:32080->80/tcp forum a02452eb7dad nasqueron/etherpad "/entrypoint.sh bin/r" 4 weeks ago Up 3 weeks 0.0.0.0:34080->9001/tcp pad 330d032afb49 nasqueron/phabricator "/usr/local/sbin/init" 4 weeks ago Up 4 weeks 443/tcp, 0.0.0.0:35080->80/tcp wolfphab b13a9f0390fe nasqueron/aphlict "node aphlict_server." 4 weeks ago Up 4 weeks 0.0.0.0:22280-22281->22280-22281/tcp aphlict 51099144b9cd nasqueron/phabricator "/usr/local/sbin/init" 4 weeks ago Up 4 weeks 443/tcp, 0.0.0.0:31080->80/tcp devcentral f96fae8dd5f2 nasqueron/mysql "/entrypoint.sh mysql" 4 weeks ago Up 4 weeks 3306/tcp acquisitariat
Could we get a configuration file for this list?
| paas/docker/systemd-unit/files/docker_start | ||
|---|---|---|
| 3 | That will be docker start <words before \n> as command, the remaining will be new commands. But xargs will work here: get-containers-list | xargs docker start | |
| paas/docker/systemd-unit/files/docker_stop | ||
| 3 | reverse | |
| paas/docker/systemd-unit/files/get-containers-list | ||
| 4 | reverse | |
| 23 | reverse | |
Comment Actions
- Revising files hierarchy
- Added files containers.conf and get-containers-list
- Adding new containers to the list : cachet, ci, and white-rabbit
Comment Actions
- Revising files hierarchy
- Added files containers.conf and get-containers-list
- Adding new containers to the list : cachet, ci, and white-rabbit