Auto-remove docker containers after run

[RixzZ]

Description

I'm using atom-beautify with beautysh on docker. Every time it executes, a new container is created and not autoremoved. The same container is not being used anymore, so after a few saves I end up with the same number of beautysh containers that times I saved a file.

Steps to Reproduce

1. Add code to Atom editor (bash in my case)
2. Run command Atom Beautify: Beautify Editor
3. A new container is created in Docker every time but they don't remove itself after executing.

Docker have a flag '--rm' you can specify when running the container so it automatically remove itself when the task finishes. Can that be

Checklist

I have:

• Tried uninstalling and reinstalling Atom Beautify to ensure it installed properly
• Reloaded (or restarted) Atom to ensure it is not a caching issue
• Searched through existing Atom Beautify Issues at https://github.com/Glavin001/atom-beautify/issues
  so I know this is not a duplicate issue
• Filled out the Input, Expected, and Actual sections above or have edited/removed them in a way that fully describes the issue.
• Generated debugging information by executing Atom Beautify: Help Debug Editor command in Atom and added link for debug.md Gist to this issue

[ghost]

Please follow the issue template provided. More specifically, update the original comment for this issue by adding a link to the required debug.md gist which includes debugging information that answers our most commonly asked questions. Thank you.

[probot-no-response]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

[ghost]

Please follow the issue template provided. More specifically, update the original comment for this issue by adding a link to the required debug.md gist which includes debugging information that answers our most commonly asked questions. Thank you.

[Glavin001]

I think the bug is in

atom-beautify/src/beautifiers/executable.coffee

Lines 451 to 460 in bb9428a

	@docker.run([
	"run",
	"--volume", "#{pwd}:#{workingDir}",
	"--volume", "#{path.resolve('/')}:#{rootPath}",
	"--workdir", workingDir,
	image,
	newArgs
	],
	Object.assign({}, options, { cmd: undefined })
	)

Looks like other users have experienced this, too: https://twitter.com/lambdafu/status/987116195538141184

[Glavin001]

I can reproduce:

❯ docker ps --all
CONTAINER ID        IMAGE                                                 COMMAND                  CREATED                  STATUS                      PORTS               NAMES
f64baf9722a0        unibeautify/elm-format                                "elm-format --yes in…"   Less than a second ago   Exited (0) 27 seconds ago                       elated_mccarthy
265d8f5a1ad4        unibeautify/elm-format                                "elm-format --help"      Less than a second ago   Exited (0) 28 seconds ago                       epic_swirles

[Glavin001]

@RixzZ You can use the following to clean up:

docker ps --all | grep "unibeautify/" | awk '{ print $1 }' | xargs docker rm

[Glavin001]

Published fix to v0.33.4