Azure-docs: libxcb

[bharatraja]

[Enter feedback here]

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: d10bd923-e9e2-3958-a9b9-1baac169b308
• Version Independent ID: f78bdb47-e841-b612-6964-9a6f1fce293f
• Content: Tutorial - Deploy Custom Vision classifier to a device using Azure IoT Edge
• Content Source: articles/iot-edge/tutorial-deploy-custom-vision.md
• Service: iot-edge
• GitHub Login: @kgremban
• Microsoft Alias: kgremban

[bharatraja]

When I follow the sample and deploy to IoT edge I get the error below. Is the Custom Vision generated docker file missing a library (libxcb)?
sudo iotedge logs classifier
Traceback (most recent call last):
File "app.py", line 10, in
from PIL import Image
File "/usr/local/lib/python3.7/site-packages/PIL/Image.py", line 93, in
from . import _imaging as core
ImportError: libxcb.so.1: cannot open shared object file: No such file or directory
Traceback (most recent call last):
File "app.py", line 10, in
from PIL import Image
File "/usr/local/lib/python3.7/site-packages/PIL/Image.py", line 93, in
from . import _imaging as core

[SatishBoddu-MSFT]

@bharatraja Thanks for the feedback! We are currently investigating and will update you shortly. If possible could you please edit the issue Title with more specific reason or error verbiage.

[SatishBoddu-MSFT]

@bharatraja I have assigned the issue to the content author @kgremban for further review and update the doc as appropriate.

[bharatraja]

BTW, here is a addl. Library I added that fixes the issue….i added libxcb1 and it fixed the issue from the autogenerated Dockerfile from model export in azure custom vision

RUN apt update && apt install -y libjpeg62-turbo libopenjp2-7 libtiff5 libatlas-base-dev libxcb1

Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

[kgremban]

@bharatraja we tried to reproduce your error a few times and weren't able to. Perhaps the library was updated on the custom vision side of things between you creating your issue and us testing it. Since there's no doc update we can make at this time, I'm going to close this issue. If you still experience that error, consider opening a support ticket or posting on a community site like stackoverflow or Microsoft Q&A where you can get troubleshooting help.

Thanks

please-close