zandbelt
commented
4 years ago we'll investigate asap. but I guess for now it is best to use the Docker images from https://hub.docker.com/r/openidcertification/op_test/tags
Closed CrowdHailer closed 4 years ago
zandbelt
commented
4 years ago we'll investigate asap. but I guess for now it is best to use the Docker images from https://hub.docker.com/r/openidcertification/op_test/tags
CrowdHailer
commented
4 years ago @zandbelt thank you. This looks a much more accessible approach for anyone with docker installed.
Is it important that you modify your host file. so that you can call it at the domain op-test?
I've run
docker run -p 60000:60000 openidcertification/op_test:v1.2.4However I cannot visit service at http://localhost:60000 ?
I did see this output from the docker run command. But it hasn't stopped the container starting so might just be warnings.
Traceback (most recent call last):
File "/usr/local/lib/python3.6/dist-packages/CherryPy-8.9.1-py3.6.egg/cherrypy/wsgiserver/__init__.py", line 2021, in start
self.tick()
File "/usr/local/lib/python3.6/dist-packages/CherryPy-8.9.1-py3.6.egg/cherrypy/wsgiserver/__init__.py", line 2090, in tick
s, ssl_env = self.ssl_adapter.wrap(s)
File "/usr/local/lib/python3.6/dist-packages/CherryPy-8.9.1-py3.6.egg/cherrypy/wsgiserver/ssl_builtin.py", line 67, in wrap
server_side=True)
File "/usr/lib/python3.6/ssl.py", line 407, in wrap_socket
_context=self, _session=session)
File "/usr/lib/python3.6/ssl.py", line 817, in __init__
self.do_handshake()
File "/usr/lib/python3.6/ssl.py", line 1077, in do_handshake
self._sslobj.do_handshake()
File "/usr/lib/python3.6/ssl.py", line 689, in do_handshake
self._sslobj.do_handshake()
OSError: [Errno 0] Errorthe modification to the hosts file is important once you start to run tests; the SSL error message is (unfortunately) merely a warning; you should use "https" rather than "http"
CrowdHailer
commented
4 years ago Interesting, I see that warning before making any requests. I wonder if it's a health check or ping I have somewhere. I will investigate.
Is there a way to start the docker container with some services already configures. Probably by mounting a volume in the appropriate place
dimaqq
commented
4 years ago It seems entropy was pulled from pypi...
Google finds some cached URLs, but pypi.org reports there's no such package...
zandbelt
commented
4 years ago yes, I was afraid of that: @rohe what's the typical way forward here?
CrowdHailer
commented
4 years ago @zandbelt is there somewhere documented that there are published images for this project? If not would adding a comment to the README about getting started be a good idea
rohe
commented
4 years ago Hmm, neither pyoidc or pyjwkest requires something called entropy. So it's a secondary requirement. Will take some time to track down and even so I'm not sure what we could do about it. There used to be an entropy package at pypi but that was a couple of years ago.
tpazderka
commented
4 years ago Although it looks like the package is actually not used and just declared as a dependency, so it should be safe to remove.
rohe
commented
4 years ago Ah, missed that! Thanks @tpazderka ! Then it should be possible to handle.
rohe
commented
4 years ago Removed the requirement. My guess is that there might be other requirements that are not needed anymore now when we demand python 3.5 or higher. PyYAML for instance.
travisspencer
commented
4 years ago Is there a fix for this? Encountering the same error on master.
This is blocking us from upgrading to get the new logout tests.
zandbelt
commented
4 years ago we'll rollout the fix to production later today or tomorrow
travisspencer
commented
4 years ago I am OK with a fix on master. We don't need it running anywhere for our local tests. Just the update here in GitHub is OK for us. Is that what you meant, @zandbelt ?
zandbelt
commented
4 years ago I see: the fix is in "otest" which is a dependency; I have pushed it here: https://github.com/openid-certification/otest/commit/908ea67c2473e213ba62a9e285c57c24fc947694 you'll need to rebuild after removing some of the Docker cache that contains otest master...
travisspencer
commented
4 years ago But, doesn't the otest submodule or dependency need to be updated here on master? We suck this repo in as a submodule to our code and build the Docker container from it. Then, we run our tests, so this is our only entry point into the test tool during our pre-certification testing.
zandbelt
commented
4 years ago oidctest master depends only on otest master, which would be cached in Docker... I know it is sub-optimal but that's why the release branch used fixed versions of dependencies
travisspencer
commented
4 years ago I'm confused. Did you just push a fix? I'm not getting it:
.../oidctest > master $ git pull Already up to date.
travisspencer
commented
4 years ago Ah, I see. Got it. The master of this module didn't change, but the Docker build process is pulling in master of the oidctest project that had the fix. I'm up now! Thanks @zandbelt !
travisspencer
commented
4 years ago From my perspective, this issue can be closed.
I have cloned the repo and checked out the branch
stable-release-1.2.x. The tag I am at isv1.2.5. When try to start the project, building the image fails.command:
error:
docker version: Docker version 19.03.6, build 369ce74a3c docker-compose version: docker-compose version 1.25.3, build d4d1b42b
full logs: