Closed qw8z5fUB closed 7 months ago
I have a fix in #260 if I can't find a full fix for compatibility, I'll merge that pinback short term and keep this open.
Can you try out the fix in #261 on your system?
Thanks, that's fixed it :+1:.
I ran:
python3 -m venv venv
source venv/bin/activate
pip install --upgrade pip
pip install git+https://github.com/osrf/rocker.git@empy4_fixes
With that I am now able to run rocker with the nvidia flag:
rocker ros:humble --nvidia
Pip freeze confirms I am in fact using empy 4:
certifi==2023.11.17
charset-normalizer==3.3.2
docker==6.1.3
empy==4.0
idna==3.6
packaging==23.2
pexpect==4.9.0
pkg_resources==0.0.0
ptyprocess==0.7.0
requests==2.31.0
rocker @ git+https://github.com/osrf/rocker.git@0e09053a4b808e49a3ac7a34667ff7a2397aec70
urllib3==2.1.0
websocket-client==1.7.0
Thanks for verifying the fix!
Oh, follow up question - would you consider updating the pypi release version to current main?
My CI is still failing because the current pypi release 0.2.12 does not include the empy fix.
Not sure how much hassle it is for you to push a new release.
Hi there, I've noticed from my CI that fresh rocker installs are failing to run rocker with the --nvidia flag.
I've traced this back to a new empy release overnight, from version 3.3.4 to 4.0: https://pypi.org/project/empy/#history
I'm not sure if this is an empy bug, or a breaking API change requiring an update in rocker, in any case I'm logging a ticket here for awareness.
Here's how I reproduce the issue on Ubuntu 20.04.6 LTS, Python 3.8.10:
This produces output:
Package versions for the above error:
Rolling back empy to the previous version resolves the issue: