fix: clarify error message when starting docker container

[unlair]

Error message was not indicating which Docker container failed to start, forcing the user to use a process of elimination to narrow down the problem.

What kind of change does this PR introduce?

Bug fix (updating error message).

What is the current behavior?

When an error is returned when starting a Docker container (e.g. #3593 the error message reads:
failed to start docker container: <some error>

What is the new behavior?

The error message reads:
failed to start docker container "<container name>": <some error>

[coveralls]

Pull Request Test Coverage Report for Build 21680522717

Details

• 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
• 7 unchanged lines in 2 files lost coverage.
• Overall coverage decreased (-0.02%) to 55.353%

---

Files with Coverage Reduction	New Missed Lines	%
internal/storage/rm/rm.go	2	80.61%
internal/gen/keys/keys.go	5	12.9%

Totals
Change from base Build 21669533478:	-0.02%
Covered Lines:	7114
Relevant Lines:	12852

---

💛 - Coveralls