Closed vigeeking closed 4 years ago
I was able to get a basic index.html page served by running: docker build -t index.html . docker run --name pipeline -d -p 8080:80 index.html
I will now look at automating this process from a shell script.
Was able to get the container running with I THINK the correct watched folder, but the ports are not exposted. I was able to get it running using: docker run -d --name=pipeline --mount source=homeAutomation,destination=/usr/share/nginx/html,readonly nginx:latest
Ports are now exposed, but the directory I'm serving is not the correct one.
To get here I used: docker run -d --name=pipeline --mount source=homeAutomation,destination=/usr/share/nginx/html,readonly -p 8080:80 nginx:latest
Note to self: I initially pasted the -p between the mount command and the input it was getting. It took me a few diagnostic steps to catch this, and is something to check for in future "wtf did I do wrong" scenarios.
second note: The above script is directory sensitive, but there does not seem to be a way to fix this, so I am accepting that friction, but may forget.
Docker is now working, setting this to master, will work with branch merging from this point.
The pipeline builds locally, but has not been tested pulling from github yet. I should have defined "done" better. Reopening.
tested, it works on local machine in new folder.
I have used the term pipeline relative to many other tasks. I need to define what the pipeline is. This task is done when I have created an item, and added it to the pipeline (by definition, this will create the pipeline)
Edit: This goal was completed, but it has not been tested to pull from github successfully. Even though the original goal is met, I don't want to leave this last piece unfinished.