Closed leomao10 closed 3 years ago
Thanks for this deep research, we will try to sort out this issue
@leomao10 new version containing the fix has been published. Let us know if it works.
Hey @Deffiss Thanks for fixing it so quick, I will let our user know about it 👍
Hey, this bitbucket user is probably us! I originally reported it to Bitbucket support on Nov 10 and their team was very helpful to solve it for us and temporarily whitelisted our repository to use older version of docker.
Very happy to see that it was reported and already fixed here. I just tried running our pipeline on a forked repository with an updated nuget package and appears to work correctly now.
Thanks @leomao10 and @Deffiss.
Hi There,
This is Leo from BitBucket Pipeline 👋
Recently, we upgrade our docker version to 19 and receive bugs reported from our users who have their integration tests failed because of following error:
We did a bit of research for the error, and found that it is because in docker 19 introduce a new change which would lead to the error mentioned above when:
'userns-remap' = 'default'
docker run -ti --domainname my.domain some-image
You can find more details in here.
Whereas in
testenvironment-docker
, we found that it set the container domain name with container name by default: https://github.com/Deffiss/testenvironment-docker/blob/c435fa665ff1bcbce2c63b31d13e1335ae705c88/src/TestEnvironment.Docker/Container.cs#L149-L161Wondering if
testenvironment-docker
can provide a way to override theDomainname
option, then we can enable docker 19 for those users with minimum changes for their integration tests.