I could (and did, see my previous responses), but I doubt it would make sense, since I don't think the Jenkins inside your container is configured to use SSL, or is it?
If you want to protect your Jenkins setup with SSL, I'd recommend running an Apache2 or NGinx webserver as a reverse proxy in front of it to handle the SSL stuff (see Jenkins documentation). This could be running directly on your Docker host, inside a container or even on a remote machine, but that's up to you.
As long as you don't have this set up, it doesn't make sense to try to connect using https://. Please first try to connect w/o SSL to confirm it's working, by using "curl http://<hostname>:8080" from a remote host. Then setup SSL.
BTW: If you change your "-p 8080:8080" to "-p 80:8080", to map the hosts port 80 to the containers port 8080, you can omit the port number when running your curl command, since 80 is the standard port for http:// (the command becomes just "curl http://<hostname>".