Open SahilChaudhari opened 4 months ago
This was due to a recent break https://github.com/docker/docker-py/issues/3256.
Please use the following temporary workaround to proceed with the build.
Add pip install requests package and pin version to <2.32.0 in build_debian.sh
sudo https_proxy=$https_proxy LANG=C chroot $FILESYSTEM_ROOT pip3 install 'docker==6.1.1' sudo https_proxy=$https_proxy LANG=C chroot $FILESYSTEM_ROOT pip3 install 'requests<2.32.0'
Thanks it worked for me.
This needs to be fixed in code. Reopening the ticket until sonic code is modified
A PR is raised to fix this already but failing PR test. submitter is working on resolving the test issue. https://github.com/sonic-net/sonic-utilities/pull/3328
BTW, requests
is also installed in docker-sonic-mgmt-framework. https://github.com/sonic-net/sonic-buildimage/blob/7d7332a6448c53856978db845685892507d27abe/dockers/docker-sonic-mgmt-framework/Dockerfile.j2#L11
Not sure, should we also use version 2.31.0 here or not.
I see the fix committed to sonic-net/sonic-utilities, but I don't see sonic-buildimage pointing to a version of sonic-utilities that has the fix. Any ETA on when this will be fixed?
I see the fix committed to sonic-net/sonic-utilities, but I don't see sonic-buildimage pointing to a version of sonic-utilities that has the fix. Any ETA on when this will be fixed?
I see there is one outstanding PR for sonic-utilities submodule update : https://github.com/sonic-net/sonic-buildimage/pull/18828 Once that gets in, or it failed and it forces to pick up the next head which will include the fix you wanted...
I see there is one outstanding PR for sonic-utilities submodule update : #18828 Once that gets in, or it failed and it forces to pick up the next head which will include the fix you wanted...
Thanks. Since this is for a build failure, will this be backported to 202305, 202311, 202405?
I see there is one outstanding PR for sonic-utilities submodule update : #18828 Once that gets in, or it failed and it forces to pick up the next head which will include the fix you wanted...
Thanks. Since this is for a build failure, will this be backported to 202305, 202311, 202405?
Please post your question to the PR and ask the Branch owner for 202305/202311 to see if this can be back ported to those branches. 202405 is not yet cut so it will have it for sure.
Instead of having the fix in sonic-utilities, why not commit the above proposed fix directly to build_debian.sh
? Then we don't need to wait on updates to submodule pointers, etc.
diff --git a/build_debian.sh b/build_debian.sh
index 6e80ab5cb..5d596e9a6 100755
--- a/build_debian.sh
+++ b/build_debian.sh
@@ -554,6 +554,7 @@ sudo https_proxy=$https_proxy LANG=C chroot $FILESYSTEM_ROOT pip3 install 'wheel
# docker Python API package is needed by Ansible docker module as well as some SONiC applications
sudo https_proxy=$https_proxy LANG=C chroot $FILESYSTEM_ROOT pip3 install 'docker==6.1.1'
+sudo https_proxy=$https_proxy LANG=C chroot $FILESYSTEM_ROOT pip3 install 'requests<2.32.0'
@yxieca, the same build issue is observed on 202205 branch, could you please help to check if we need to cherry-pick this fix to 202205 - https://github.com/sonic-net/sonic-utilities/pull/3328?
Instead of having the fix in sonic-utilities, why not commit the above proposed fix directly to
build_debian.sh
? Then we don't need to wait on updates to submodule pointers, etc.diff --git a/build_debian.sh b/build_debian.sh index 6e80ab5cb..5d596e9a6 100755 --- a/build_debian.sh +++ b/build_debian.sh @@ -554,6 +554,7 @@ sudo https_proxy=$https_proxy LANG=C chroot $FILESYSTEM_ROOT pip3 install 'wheel # docker Python API package is needed by Ansible docker module as well as some SONiC applications sudo https_proxy=$https_proxy LANG=C chroot $FILESYSTEM_ROOT pip3 install 'docker==6.1.1' +sudo https_proxy=$https_proxy LANG=C chroot $FILESYSTEM_ROOT pip3 install 'requests<2.32.0'
Not really. Just adding an upper bound to requests may fix this case but the problem would quickly reappear because of the clear lack of pinning the indirect dependencies installed by pip. To avoid these common issues related to pip, I would highly recommend the use of upper-constraints as OpenStack (or OPNFV) has done for years.
I just sent an email to the mailing lists, but it doesn't look like broadcasted yet (@yxieca is there a manual mail validation ?)
I see the fix committed to sonic-net/sonic-utilities, but I don't see sonic-buildimage pointing to a version of sonic-utilities that has the fix. Any ETA on when this will be fixed?
I see there is one outstanding PR for sonic-utilities submodule update : #18828 Once that gets in, or it failed and it forces to pick up the next head which will include the fix you wanted...
same comments as https://github.com/sonic-net/sonic-buildimage/issues/19028#issuecomment-2144617202
I've opened #19181 which upgrades docker
to 7.1.0, which has the fix for requests 2.32.0. This should fix this issue fully.
Running Docker inside chroot results in "requests.exceptions.InvalidURL: Not supported URL scheme http+docker" due to Docker client failing to connect to Docker daemon.
The workspace was working fine till 20th May, On 21st May build started failing with below issue.
Steps to reproduce the issue:
1.export MIRROR_SNAPSHOT=y && NOJESSIE=1 NOSTRETCH=1 make target/sonic-pensando.tar
can someone please help?