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.

Sign up for GitHub

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

Jump to bottom

Replace base image with Ubuntu #3

Closed
mtscout6 opened this issue Nov 17, 2014 · 0 comments
Closed

Replace base image with Ubuntu #3

mtscout6 opened this issue Nov 17, 2014 · 0 comments
Assignees
@mtscout6
Labels
enhancement
Milestone
Get Docker Offici...

Comments

@mtscout6
Copy link
Member

Since the phusion/baseimage has not been sanctioned as an Official Docker Repo, we need to change to one that is.

This will break the VNC support used in debugging.

An option to mitigate this until #2 is resolved is to define an image with VNC support that derives from the sanctioned node images, to which we do not seek official sanctions by docker. Then when #2 is resolved we can remove those images.
@mtscout6 mtscout6 self-assigned this Nov 17, 2014
mtscout6 added a commit that referenced this issue Nov 19, 2014
@mtscout6
Change selenium base image to FROM ubuntu:14.04
e81541f 
Use an officially sanctioned base image as per Docker Official Repo
Guidelines.

Part of #3
mtscout6 added a commit that referenced this issue Nov 19, 2014
@mtscout6
Change Hub to run Selenium server directly
c47d52a 
Remove init script in favor of directly running the Hub via the
Dockerfile CMD.

Part of #3
mtscout6 added a commit that referenced this issue Nov 19, 2014
@mtscout6
Change Chrome Node to run Selenium Node Directly
db20142 
Remove init script for running Selenium node in favor of running the jar
directly.

Part of #3
mtscout6 added a commit that referenced this issue Nov 19, 2014
@mtscout6
Change Firefox Node to run Selenium Node Directly
d93ff04 
Remove init script for running Selenium node in favor of running the jar
directly.

Part of #3
mtscout6 added a commit that referenced this issue Nov 19, 2014
@mtscout6
Makefile cleanup
517c7ee 
- Remove unused clean task
+ Add ci task
+ Add build and test tasks to .PHONY

Part of #3
mtscout6 added a commit that referenced this issue Nov 19, 2014
@mtscout6
Updated README with image name changes and usage
2e3d38c 
Part of #3
@mtscout6 mtscout6 mentioned this issue Nov 19, 2014
Closed
mtscout6 added a commit that referenced this issue Nov 19, 2014
@mtscout6
Only expose port 4444 in the Hub container
ea92463 
The node images shouldn't be exposing the 4444 port since they don't
even listen on that port.

Part of #3
mtscout6 added a commit that referenced this issue Nov 20, 2014
@mtscout6
Add debug images with VNC server
e3cef83 
These debug images are not meant to be included in the official docker
supported debug solution, they are merely a stop gap till #2 is
resolved.

Part of #3
mtscout6 added a commit that referenced this issue Nov 20, 2014
@mtscout6
Update README with debugging instructions
58ad853 
Part of #3
mtscout6 added a commit that referenced this issue Nov 20, 2014
@mtscout6
Add README to NodeDebug folder
e6b28dc 
The NodeDebug folder is not intended to stand as a standalone dockerfile
folder. It is a template used to generate the NodeChromeDebug and
NodeFirefoxDebug folders.

Note that the NodeChromeDebug and NodeFirefoxDebug folders are commited
into the repo for the purposes of simplified builds on hub.docker.com.

Part of #3
mtscout6 added a commit that referenced this issue Nov 20, 2014
@mtscout6
Change Chrome Node to run Selenium Node Directly
25495f1 
Remove init script for running Selenium node in favor of running the jar
directly.

Part of #3
mtscout6 added a commit that referenced this issue Nov 20, 2014
@mtscout6
Change Firefox Node to run Selenium Node Directly
654897c 
Remove init script for running Selenium node in favor of running the jar
directly.

Part of #3
mtscout6 added a commit that referenced this issue Nov 20, 2014
@mtscout6
Makefile cleanup
3bb5ef3 
- Remove unused clean task
+ Add ci task
+ Add build and test tasks to .PHONY

Part of #3
mtscout6 added a commit that referenced this issue Nov 20, 2014
@mtscout6
Updated README with image name changes and usage
c902ae2 
Part of #3
mtscout6 added a commit that referenced this issue Nov 20, 2014
@mtscout6
Only expose port 4444 in the Hub container
41b5b4b 
The node images shouldn't be exposing the 4444 port since they don't
even listen on that port.

Part of #3
mtscout6 added a commit that referenced this issue Nov 20, 2014
@mtscout6
Add debug images with VNC server
5eb0ab8 
These debug images are not meant to be included in the official docker
supported debug solution, they are merely a stop gap till #2 is
resolved.

Part of #3
mtscout6 added a commit that referenced this issue Nov 20, 2014
@mtscout6
Update README with debugging instructions
9b1bbfa 
Part of #3
mtscout6 added a commit that referenced this issue Nov 20, 2014
@mtscout6
Add README to NodeDebug folder
3ff794a 
The NodeDebug folder is not intended to stand as a standalone dockerfile
folder. It is a template used to generate the NodeChromeDebug and
NodeFirefoxDebug folders.

Note that the NodeChromeDebug and NodeFirefoxDebug folders are commited
into the repo for the purposes of simplified builds on hub.docker.com.

Part of #3
Remi-p added a commit to Remi-p/docker-selenium that referenced this issue Jun 7, 2017
@Remi-p
Moving config generation in docker files
73e0c87 
This allow random users to launch the images.
The behavior is needed for OpenShift.
Cf. issue SeleniumHQ#3 from ddavison/selenium-openshift-templates
@lock lock bot locked and limited conversation to collaborators Aug 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@mtscout6 mtscout6

Labels
enhancement
Projects
None yet
Milestone
Get Docker Official Repository Signoff
Development

No branches or pull requests
1 participant
@mtscout6