Closed slimslenderslacks closed 5 years ago
I have seen two cases where the push is not successful but the goal still completes successfully. Here's one (blob upload unknown)
b3c5147f2ed1: Layer already exists -- 11/24/2018 02:24:02.436 | 41f50d293d3a: Layer already exists 11/24/2018 02:24:02.645 | 5251addbe073: Layer already exists 11/24/2018 02:24:02.866 | d5ce7f246067: Layer already exists 11/24/2018 02:24:03.088 | f1b91f8d903c: Layer already exists 11/24/2018 02:24:03.275 | 6adc2bf29e0f: Pushed 11/24/2018 02:24:07.285 | f82e03a2add6: Pushed 11/24/2018 02:24:16.538 | 8884dcc2b6ca: Pushed 11/24/2018 02:24:39.777 | 5e053cb239b1: Pushed 11/24/2018 02:24:40.358 | blob upload unknown 11/24/2018 02:24:40.543 | /-- 11/24/2018 02:24:40.543 | Invoking after project listener: npm install
and this one has an error parsing below
ada50b9a12a2: Layer already exists -- 11/24/2018 01:46:15.538 | 48445ea453ab: Layer already exists 11/24/2018 01:46:15.654 | b3c5147f2ed1: Layer already exists 11/24/2018 01:46:15.707 | 41f50d293d3a: Layer already exists 11/24/2018 01:46:15.831 | d5ce7f246067: Layer already exists 11/24/2018 01:46:15.833 | 5251addbe073: Layer already exists 11/24/2018 01:46:15.889 | f1b91f8d903c: Layer already exists 11/24/2018 01:46:16.533 | e5fba150d040: Pushed 11/24/2018 01:46:16.592 | 06bb5cc1493f: Pushed 11/24/2018 01:46:16.597 | error parsing HTTP 404 response body: invalid character 'p' after top-level value: "404 page not found\n" 11/24/2018 01:46:16.707 | /-- 11/24/2018 01:46:16.707 | Invoking after project listener: npm install 11/24/2018 01:46:16.710 | Result: Success
We think this may have been an issue with docker hub itself but should the failure handler for the docker push goal have noticed this?
I have seen two cases where the push is not successful but the goal still completes successfully. Here's one (blob upload unknown)
and this one has an error parsing below
We think this may have been an issue with docker hub itself but should the failure handler for the docker push goal have noticed this?