-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Override localstack image using TestcontainersConfiguration #1603
Comments
Hi @wavetylor. Sure! I think this would be fine. If you'd like to raise a PR that would be great. I don't think there should be any serious gotchas. The only thing is that the tag/version part probably belongs in the Please have a glance over any Localstack related issues/PRs we have (e.g. #1504) so that you can get a sense of other forthcoming changes - not because it impacts this change directly, but more so you can be confident that we'll remain compatible with your custom image! |
@rnorth sounds good. Already working on the changes. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this is a mistake, please reply to this comment to keep it open. If there isn't one already, a PR to fix or at least reproduce the problem in a test case will always help us get back on track to tackle this. |
Nowadays, testcontainers support image name substitution which solves issues like this. @wavetylor feel free to reopen if I missed something. |
Currently using the Localstack module is not possible in a situation where pulling public docker images is not possible.
Testcontainer has a facility to address this, testcontainer.properties, but localstack doesn't take advantage of this.
It would be excellent if this were the case!
The text was updated successfully, but these errors were encountered: