Update TorchServe dev container

[sachanub]

Description

Please read our CONTRIBUTING.md prior to creating your first pull request.

Please include a summary of the feature or issue being fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes #(issue)

The following changes have been made in this PR:

• Moved the dev container stage to Dockerfile from Dockerfile.dev
• While cloning the TorchServe repo in the Docker container, added the --recursive option to also pull the third party googleapis repository. If this is not done, running the regression tests inside the container will fail with this error:

0.377 google/rpc/status.proto: File not found.
0.377 inference.proto:6:1: Import "google/rpc/status.proto" was not found or had errors.
0.377 inference.proto:32:14: "google.rpc.Status" is not defined.

• Update the build_image.sh script to build the dev container using Dockerfile instead of Dockerfile.dev.
• Removed any codebuild and Dockerfile.benchmark related code from the build_image.sh script.
• Updated the version of intel_extension_for_pytorch to 2.1.0.
• Remove the section related to codebuild images from the README.md file.
• Add a deprecation notice for Dockerfile.dev in the README.md file.

Type of change

Please delete options that are not relevant.

• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

Feature/Issue validation/testing

Please describe the Unit or Integration tests that you ran to verify your changes and relevant result summary. Provide instructions so it can be reproduced.
Please also list any relevant details for your test configuration.

Tested the dev container by running the regression tests in it. Followed these steps to build and test the dev container:

./build_image.sh -g -bt dev
docker run -it --rm --gpus=all --user root pytorch/torchserve:dev-gpu /bin/bash
apt-get update 
DEBIAN_FRONTEND=noninteractive apt-get install --no-install-recommends -y wget nodejs npm zip unzip
npm install -g newman@5.3.2 newman-reporter-htmlextra markdown-link-check
cd /serve
python test/regression_tests.py

The logs of the test run can be found here regression_tests_logs.txt

Tested the dev IPEX container by running https://github.com/pytorch/serve/blob/master/test/pytest/test_example_intel_extension_for_pytorch.py in it. Followed these steps to build and test the dev IPEX container:

./build_image.sh -bt dev -ipex -t pytorch/torchserve:dev-ipex
docker run -it --rm --privileged --user root pytorch/torchserve:dev-ipex /bin/bash
mkdir -p /home/model-server/tmp/workspace/model_store
cd /home/model-server/tmp/workspace/model_store/
curl -O https://torchserve.pytorch.org/mar_files/resnet-18.mar
cd /serve/test/pytest
pytest -rA test_example_intel_extension_for_pytorch.py

The logs of the IPEX tests can be found here regression_test_ipex_logs.txt

[agunapal]

Hi @sachanub Thanks for refactoring this!
Can you please run the regression tests on the dev image and attach the logs. You can refer to the nightly docker regression workflow.

[sachanub]

Hi @sachanub Thanks for refactoring this! Can you please run the regression tests on the dev image and attach the logs. You can refer to the nightly docker regression workflow.

Hi @agunapal. I just attached the regression test logs in the PR description. I have also included the testing steps. Thanks!

[agunapal]

Hi @sachanub Thanks for refactoring this! Can you please run the regression tests on the dev image and attach the logs. You can refer to the nightly docker regression workflow.

Hi @agunapal. I just attached the regression test logs in the PR description. I have also included the testing steps. Thanks!

Great!
Can you please enable/run this ipex test and see if it works. You can run just this single test in the container. Currently, its disabled for docker regression, but this should work in the dev image I suppose.
https://github.com/pytorch/serve/blob/master/test/pytest/test_example_intel_extension_for_pytorch.py

[sachanub]

Hi @sachanub Thanks for refactoring this! Can you please run the regression tests on the dev image and attach the logs. You can refer to the nightly docker regression workflow.

Hi @agunapal. I just attached the regression test logs in the PR description. I have also included the testing steps. Thanks!

Great! Can you please enable/run this ipex test and see if it works. You can run just this single test in the container. Currently, its disabled for docker regression, but this should work in the dev image I suppose. https://github.com/pytorch/serve/blob/master/test/pytest/test_example_intel_extension_for_pytorch.py

Sounds good. I will run the IPEX test and attach the logs.

[sachanub]

Hi @sachanub Thanks for refactoring this! Can you please run the regression tests on the dev image and attach the logs. You can refer to the nightly docker regression workflow.

Hi @agunapal. I just attached the regression test logs in the PR description. I have also included the testing steps. Thanks!

Great! Can you please enable/run this ipex test and see if it works. You can run just this single test in the container. Currently, its disabled for docker regression, but this should work in the dev image I suppose. https://github.com/pytorch/serve/blob/master/test/pytest/test_example_intel_extension_for_pytorch.py

Sounds good. I will run the IPEX test and attach the logs.

Attached logs of IPEX test run in PR description.

[agunapal]

Thanks @sachanub ! LGTM