When building custom Java destination connector, after build is successful, I get the following error: 21: start dockerd-entrypoint.sh dockerd --log-level=error --host=tcp://0.0.0.0:2375 --tls=false ERROR: release: exit code: 1

pipelines: Dagger Command build failed
Traceback (most recent call last):
  File "/root/.cache/pypoetry/virtualenvs/pipelines-VouYb7oL-py3.10/lib/python3.10/site-packages/dagger/client/_core.py", line 139, in execute
    result = await self.conn.session.execute(query)
  File "/root/.cache/pypoetry/virtualenvs/pipelines-VouYb7oL-py3.10/lib/python3.10/site-packages/dagger/client/_session.py", line 126, in execute
    return await (await self.get_session()).execute(query)
  File "/root/.cache/pypoetry/virtualenvs/pipelines-VouYb7oL-py3.10/lib/python3.10/site-packages/gql/client.py", line 1639, in execute
    raise TransportQueryError(
gql.transport.exceptions.TransportQueryError: {'message': 'stop: release: exit code: 1', 'locations': [{'line': 26, 'column': 23}], 'path': ['container', 'from', 'withEnvVariable', 'withExec', 'withExposedPort', 'withMountedCache', 'withMountedCache', 'withNewFile', 'withExec', 'asService', 'stop']}

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/opt/airbyte/airbyte-ci/connectors/pipelines/pipelines/cli/dagger_pipeline_command.py", line 48, in invoke
    pipeline_success = await super().invoke(ctx)
  File "/root/.cache/pypoetry/virtualenvs/pipelines-VouYb7oL-py3.10/lib/python3.10/site-packages/asyncclick/core.py", line 1485, in invoke
    return await ctx.invoke(self.callback, **ctx.params)
  File "/root/.cache/pypoetry/virtualenvs/pipelines-VouYb7oL-py3.10/lib/python3.10/site-packages/asyncclick/core.py", line 824, in invoke
    rv = await rv
  File "/opt/airbyte/airbyte-ci/connectors/pipelines/pipelines/airbyte_ci/connectors/build_image/commands.py", line 72, in build
    await run_connectors_pipelines(
  File "/opt/airbyte/airbyte-ci/connectors/pipelines/pipelines/airbyte_ci/connectors/pipeline.py", line 121, in run_connectors_pipelines
    await dockerd_service.stop()
  File "/root/.cache/pypoetry/virtualenvs/pipelines-VouYb7oL-py3.10/lib/python3.10/site-packages/dagger/client/_guards.py", line 113, in async_wrapper
    return await bear(*args, **kwargs)
  File "<@beartype(dagger.client.gen.Service.stop) at 0x7f7fd962fd90>", line 11, in stop
  File "/root/.cache/pypoetry/virtualenvs/pipelines-VouYb7oL-py3.10/lib/python3.10/site-packages/dagger/client/gen.py", line 4701, in stop
    _id = await _ctx.execute(ServiceID)
  File "/root/.cache/pypoetry/virtualenvs/pipelines-VouYb7oL-py3.10/lib/python3.10/site-packages/dagger/client/_core.py", line 164, in execute
    raise error from e
dagger.QueryError: stop: release: exit code: 1

How to fix the following error?

The error you're encountering seems to be related to the

dockerd

service not completing successfully during the build process. This issue has been addressed in a previous GitHub issue where similar errors were reported. ### Solution: The problem was mitigated by using a single

dockerd

service instead of one per connector. This change allowed the build process to complete without encountering the errors you described. ### Steps to Fix: 1. Update your build configuration to use a single

dockerd

service for all connectors instead of creating a new service for each connector. 2. Refer to the GitHub Pull Request that fixed this issue for more details: [GitHub Pull Request #27021](https://github.com/airbytehq/airbyte/pull/27021). ### Example: Here is a summary of the relevant information from the GitHub issue and the solution: > Comment by CONTRIBUTOR: > Closing as [GitHub Pull Request #27021](https://github.com/airbytehq/airbyte/pull/27021) fixed the problem: using a single dockerd service instead of one per connector mitigated the problem and we were able to run a full nightly build without these errors. By following these steps and updating your build configuration, you should be able to resolve the

dockerd

service error and successfully build your custom Java destination connector. For more detailed instructions on building a Java destination connector, you can refer to the [Airbyte documentation](https://docs.airbyte.com/connector-development/tutorials/building-a-java-destination#summary).