Commit 08ed2bc
committed
cli/command/container: make injecting config.json failures a warning
Prior to 1a502e9, failing to write the
container-ID to a file would return an error. After that change, we could
end up in a situation where the container was created successfully, but
we failed to inject the `config.json`. This failure would be returned as
an error, but the container was created (but no ID returned due to the error).
This patch changes the error to a warning; while not "ideal" (the container
is created, but in a "partial" state), we also shouldn't consider it to be
a hard failure; proceed as normal, to allow the user to either use the
container as-is, or to delete the container and try again.
Alternatively, we could join these errors, but the result will be ambiguous
in either case (container created, but an error occurred after the fact).
Signed-off-by: Sebastiaan van Stijn <[email protected]>1 parent 0312e3d commit 08ed2bc
1 file changed
+7
-10
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
363 | 363 | | |
364 | 364 | | |
365 | 365 | | |
366 | | - | |
367 | | - | |
368 | | - | |
369 | | - | |
370 | | - | |
371 | 366 | | |
372 | 367 | | |
373 | | - | |
| 368 | + | |
374 | 369 | | |
375 | | - | |
376 | | - | |
377 | | - | |
378 | | - | |
| 370 | + | |
| 371 | + | |
379 | 372 | | |
380 | 373 | | |
| 374 | + | |
| 375 | + | |
| 376 | + | |
381 | 377 | | |
| 378 | + | |
382 | 379 | | |
383 | 380 | | |
384 | 381 | | |
| |||
0 commit comments