-
-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GenericContainer broken after upgrade from 10.9 to 10.10 #785
Comments
Hi @jonesbusy, I gotta say I'm stumped by this one 😄 These are the changes between 10.9 and 10.10 (https://github.com/testcontainers/testcontainers-node/releases/tag/v10.10.0):
There are no changes which would affect how a container runtime is resolved, which is what the error in this issue describes. The features are 2 additional modules which do not affect the core. The bug fix resolves whether or not images should be force pulled, something which happens after a container runtime is resolved. The new SSHD image affects the port forwarding functionality which you do not use. The dependency updates are all minor. The core dependencies have not even been updated. These changes have all passed the builds and smoke tests. I would like some more evidence that this is an issue with Testcontainers and not a change to your kubedock environment before investigating further. |
Sure I will provide evidence Could it be minor dependencies upgraded in #780 ? No change on the infrastructure. Basically renovate found the upgrade. This is the only package upgraded and it's dependencies The main branch is building (I've run it again to be sure. All works with 10.9) The only difference I can see on the DEBUG log is the On the renovate branch On main branch with 10.9 everything is good It happens on my 2 application using testcontainers (Spotify Backstage and one very simple Vite application). Same error Despite
Do you think we can get more logs why the Regards, |
@jonesbusy can you provide you gitlab ci job configuration? I have the same issue on
|
Hi @zotijs I'm not using gitlab. I have Jenkins and K8S agent and use https://github.com/joyrex2001/kubedock to proxy the docker socket call to Kubernetes and create testcontainers The only vars I'm using on my
|
@cristianrgreco I will try to create a reproduction repository, because the repository that I am having the issue is private |
Adding more logs I get On 10.10.0
On 10.9.0
Not sure it help. Response is identical |
@cristianrgreco sorry for the delayed response. So a similar setup to what you have provided works for me too, gitlab-pipeline. I will create a branch with something similar to what I am actually doing in the private repo. But I am wondering if the issue is the group runners that we are using inside the organization. Anyhow I will come back with a more realistic example |
Hi, This is the logs after testing the 10.10.1
Any idea ? |
@jonesbusy That's progress, seems there's some issue with the configuration used by the |
@cristianrgreco Sure I will try as soon as it's released. Thanks |
Thanks @jonesbusy. Released in 10.10.2 |
This is the stackstrace of 10.10.2
|
Thanks @jonesbusy, turns out this is your issue: ab46673#diff-07adb1d2976c5e124c3804996a054095cdc770c58ec8a1b7af5c24f37da21ee7R109, added as part of the Ollama module. Will be fixed in #795. Thanks for your help in debugging this one, I'm happy with the error logs we've achieved around the container runtime |
Will leave issue open until released and fix confirmed. ETA for release within next few hours. |
@jonesbusy Please try 10.10.3 |
Thanks to you for raising such a detailed issue and for helping so much in debugging, always a pleasure! 🙂 |
Hi,
I've facing an issue after upgrade testcontainer node from 10.9 to 10.10 which any other changes
Expected Behaviour
Same as 10.9.0, it should work
Actual Behaviour
Doesn't work, tested with different framework (Backstage and one JS vite application). It's the same
Testcontainer Logs
This line is different from
On 10.9 is
Steps to Reproduce
On code
Environment Information
I can provide more details if needed
Thanks
The text was updated successfully, but these errors were encountered: