Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support docker swarm #9

Closed
sargreal opened this issue Sep 4, 2020 · 2 comments · Fixed by #11
Closed

Support docker swarm #9

sargreal opened this issue Sep 4, 2020 · 2 comments · Fixed by #11
Milestone
1.7

Comments

@sargreal
Copy link
Member

sargreal commented Sep 4, 2020

Docker swarm is an alternative/ more scalable container orchestration than docker-compose. It should also be supported with corresponding utilities.

It is currently only possible to stop containers. Possible additions for docker swarm or also in general are:

  • execute job in container (for example set maintenance mode or execute backup utility in the container)
  • scale service

Passcodes are currently stored in environment variables. It should also be possible to use _FILE environment variables
@sargreal sargreal added this to the 1.7 milestone Sep 4, 2020
sargreal added a commit that referenced this issue Sep 6, 2020
@sargreal
Reorganise and improve database images
edc1fa6 
- specify the database to backup (only mysql)
- specify the source variable in which to store the database dumps
- use env check globally
- add support for docker secrets (see #9, includes database passwords,
 gpg private key and passphrase)
- remove mysql restore script since it does not work and is obsolete
 because of restore command

see #5
@sargreal
Copy link
Member Author

Support for docker swarm now includes:

  • utility to get task of service
  • enable file_env variables for passwords and targets

Scaling and directly executing is not included because of unusefulness with cli options

@sargreal sargreal mentioned this issue Sep 26, 2020
Merged
@dreadedhamish
Copy link

Is there documentation for this?
Does "utility to get task of service" overcome the issue of not being able to stop and start containers using VOLUMERIZE_CONTAINERS because swarm adds a hash to the container name which is unpredictable?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
1.7
Development

Successfully merging a pull request may close this issue.

1.7 Fekide/volumerize
2 participants
@dreadedhamish @sargreal