-
Notifications
You must be signed in to change notification settings - Fork 1k
chore: publish official jammy image #1477
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
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
hid some debug comments; jammy wk failures will likely be resolved by microsoft/playwright#16228 |
Are jammy images built and named correctly? From changelog I see that |
Should be! Please file an issue showing what you do and how it fails! |
@aslushnikov created an issue: #1518 |
Resolves #1294.
For now, we leave
focal
as the default docker image. When v1.25 is announced, we can notify users the default base image will be changing in some future release (v1.26?) to jammy. (We should coordinate this across language ports.)As of this writing, Python 3.10 is what ships in our jammy image.
Testing: