[
https://issues.apache.org/jira/browse/FLINK-34569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17825887#comment-17825887
]
Rob Young commented on FLINK-34569:
-----------------------------------
Hi, I've had a look into it and I think the repeated:
parse error: Invalid numeric literal at line 1, column 6
Error: No such container:
is a symptom of a failure to start the aws-cli image, from earlier in the logs:
{code:java}
2024-03-02T04:10:55.5496990Z Unable to find image 'banst/awscli:latest' locally
2024-03-02T04:10:56.3857380Z docker: Error response from daemon: Head
"https://registry-1.docker.io/v2/banst/awscli/manifests/latest": read tcp
10.1.0.97:33016->54.236.113.205:443: read: connection reset by peer.
2024-03-02T04:10:56.3857877Z See 'docker run --help'.
2024-03-02T04:10:56.4586492Z Error: No such object:{code}
this means that the `AWSCLI_CONTAINER_ID` was empty and hence the error `Error:
No such container:` from the docker exec. The failed docker exec in the
subshell does not cause a failure, for example:
{code:java}
export ABC=$(docker exec -it "" bash)
Error: No such container:
[roby@roby flink-end-to-end-tests]$ echo $?
0 {code}
I tested locally by changing `banst/awscli` to a nonexistant name like
`banstz/awscli`, which produces similar output.
I have a branch which fails fast if `AWSCLI_CONTAINER_ID` is unset/empty after
the export and adds a single naive retry of `aws_cli_start`, since it looks
like a transient network error. Keen to create a PR if that approach sounds
okay to you.
> 'Streaming File Sink s3 end-to-end test' failed
> -----------------------------------------------
>
> Key: FLINK-34569
> URL: https://issues.apache.org/jira/browse/FLINK-34569
> Project: Flink
> Issue Type: Bug
> Components: Tests
> Affects Versions: 1.19.0
> Reporter: Matthias Pohl
> Priority: Critical
> Labels: test-stability
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=58026&view=logs&j=af184cdd-c6d8-5084-0b69-7e9c67b35f7a&t=0f3adb59-eefa-51c6-2858-3654d9e0749d&l=3957
> {code}
> Mar 02 04:12:57 Waiting until all values have been produced
> Unable to find image 'stedolan/jq:latest' locally
> Error: No such container:
> docker: Error response from daemon: Get "https://registry-1.docker.io/v2/":
> read tcp 10.1.0.97:42214->54.236.113.205:443: read: connection reset by peer.
> See 'docker run --help'.
> Mar 02 04:12:58 Number of produced values 0/60000
> Error: No such container:
> Unable to find image 'stedolan/jq:latest' locally
> latest: Pulling from stedolan/jq
> [DEPRECATION NOTICE] Docker Image Format v1, and Docker Image manifest
> version 2, schema 1 support will be removed in an upcoming release. Suggest
> the author of docker.io/stedolan/jq:latest to upgrade the image to the OCI
> Format, or Docker Image manifest v2, schema 2. More information at
> https://docs.docker.com/go/deprecated-image-specs/
> 237d5fcd25cf: Pulling fs layer
> [...]
> 4dae4fd48813: Pull complete
> Digest:
> sha256:a61ed0bca213081b64be94c5e1b402ea58bc549f457c2682a86704dd55231e09
> Status: Downloaded newer image for stedolan/jq:latest
> parse error: Invalid numeric literal at line 1, column 6
> Error: No such container:
> parse error: Invalid numeric literal at line 1, column 6
> Error: No such container:
> parse error: Invalid numeric literal at line 1, column 6
> [...]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
