You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now CircleCI uses setup_remote_docker environment, but this stops the client access the container exposed port and always get connection refused error when test tries to access the container exposed port.
We need to look at if change to machine executor can fix these issues without break other things:
machine: # executor type
image: ubuntu-2004:202010-01
The property 'containerless.skip.tests' can be introduced to skip all tests under containerless module until we found a solution to get all tests work on CircleCI.
The text was updated successfully, but these errors were encountered:
Now CircleCI uses setup_remote_docker environment, but this stops the client access the container exposed port and always get connection refused error when test tries to access the container exposed port.
We need to look at if change to machine executor can fix these issues without break other things:
The property 'containerless.skip.tests' can be introduced to skip all tests under containerless module until we found a solution to get all tests work on CircleCI.
The text was updated successfully, but these errors were encountered: