Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Latest version of jamesdbloom/mockserver fails to start #435

Closed
pvdlg opened this issue Feb 12, 2018 · 1 comment
Closed

Latest version of jamesdbloom/mockserver fails to start #435

pvdlg opened this issue Feb 12, 2018 · 1 comment

Comments

@pvdlg
Copy link

pvdlg commented Feb 12, 2018

Running the command docker run -d -P jamesdbloom/mockserver:latest give the following output in the docker container and stop.

2018-02-12T19:48:31.716748276Z 
java  -Dfile.encoding=UTF-8 -jar /opt/mockserver/mockserver-netty-jar-with-dependencies.jar -serverPort 1080 -logLevel INFO
2018-02-12T19:48:31.716832634Z 
   java -jar <path to mockserver-jetty-jar-with-dependencies.jar> [-serverPort <port>] [-proxyPort <port>] [-proxyRemotePort <port>] [-proxyRemoteHost <hostname>]
                                                                                       
     valid options are:                                                                
        -serverPort <port>           Specifies the HTTP and HTTPS port(s) for the      
                                     MockServer. Port unification is used to           
                                     support HTTP and HTTPS on the same port(s).       
                                                                                       
        -proxyPort <port>            Specifies the HTTP, HTTPS, SOCKS and HTTP         
                                     CONNECT port for proxy. Port unification          
                                     supports for all protocols on the same port.      
                                                                                       
        -proxyRemotePort <port>      Specifies the port to forward all proxy           
                                     requests to (i.e. all requests received on        
                                     portPort). This setting is used to enable         
                                     the port forwarding mode therefore this           
                                     option disables the HTTP, HTTPS, SOCKS and        
                                     HTTP CONNECT support.                             
                                                                                       
        -proxyRemoteHost <hostname>  Specified the host to forward all proxy           
                                     requests to (i.e. all requests received on        
                                     portPort). This setting is ignored unless         
                                     proxyRemotePort has been specified. If no         
                                     value is provided for proxyRemoteHost when        
                                     proxyRemotePort has been specified,               
                                     proxyRemoteHost will default to "localhost".    
                                                                                       
   i.e. java -jar ./mockserver-jetty-jar-with-dependencies.jar -serverPort 1080 -proxyPort 1090 -proxyRemotePort 80 -proxyRemoteHost www.mock-server.com

Everything works ok with jamesdbloom/mockserver:mockserver-5.3.0

pvdlg added a commit to semantic-release/semantic-release that referenced this issue Feb 12, 2018
pvdlg added a commit to semantic-release/semantic-release that referenced this issue Feb 12, 2018
jamesdbloom added a commit that referenced this issue Feb 12, 2018
…t tag prior to new release of current SNAPSHOT version
@jamesdbloom
Copy link
Collaborator

This is now fixed, however it'll be at most 1 hour until the docker hub build completes and updates the latest version.

evan-gerard added a commit to evan-gerard/Semantic-Release that referenced this issue May 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants