-
Notifications
You must be signed in to change notification settings - Fork 33
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
Changed decoding to UTF-8 #366
Conversation
Hi, As far as I know, Docker only uses ASCII for image and container IDs. If this is required, it is probably that it read the wrong thing instead of the ID. Do you have a traceback or an example where an error happens? |
Hey! Thank you for the quick reply. Yep, when trying to do
The code that i am trying to run is really simple: It's just an R script that outputs a plot of some example data:
As i said, it works fine when i change encoding to UTF-8. My system has Norwegian localization, but i can't really see how that would affect docker? |
Same result with a different workflow: Trows same exception, but works after changing the decoding. |
Ah, it's the JSON! That makes more sense. I forgot that was also in there. |
The `docker inspect` output contains a lot of information, which is not necessarily all ASCII.
Thanks for the fix @Peder2911, this Hopefully this is always UTF-8 and not locale-dependent, but this is not so easy to test (and who uses something else than UTF-8 nowadays?) |
I am so happy to have been able to contribute to this excellent project. You are doing great work @remram44! |
I changed the decoding done in the docker unpacker to UTF-8 from ascii.
The unpacker wasn't working for me until i did this (localization
issue?) Is there any reason not to use UTF-8 decoding ihere?