Lightning docker image's s3 support is broken: 'AioClientCreator' object has no attribute '_register_lazy_block_unknown_fips_pseudo_regions' #10852
Unanswered
akyrola
asked this question in
Lightning Trainer API: Trainer, LightningModule, LightningDataModule
Replies: 1 comment
-
Found out that this works:
Found it from here: Might be good idea to include the boto and s3sf on the docker image? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I was previously using docker image pytorchlightning/pytorch_lightning happily and submitting s3:// urls for tensorboard and checkpoint directories. However, this week this is failing due to apparent backward or forward incompatibility issue with boto (?).
I do run "pip install boto s3fs" on the docker image, as those are not present on the image (I think they should be).
I wonder if you have any advice?
Beta Was this translation helpful? Give feedback.
All reactions