Applied minor fixes to readme of golang and gcc
This commit is contained in:
parent
6e82955a93
commit
571b4bae20
|
|
@ -12,13 +12,13 @@ For this image, the most straight-forward use is to use a gcc container as both
|
|||
FROM gcc
|
||||
ADD . /usr/src/myapp
|
||||
WORKDIR /usr/src/myapp
|
||||
RUN gcc -o executable main.c
|
||||
CMD ["./executable"]
|
||||
RUN gcc -o myapp main.c
|
||||
CMD ["./myapp"]
|
||||
|
||||
Then run the commands to build and run the docker image.
|
||||
|
||||
docker build -t my-gcc-app .
|
||||
docker run -it --rm --name my-running-app my-gcc-app ./myapp
|
||||
docker run -it --rm --name my-running-app my-gcc-app
|
||||
|
||||
## Compile your app inside the docker container.
|
||||
|
||||
|
|
@ -28,4 +28,4 @@ It is not always appropriate to run your app inside a container. In instances wh
|
|||
|
||||
This will add your current directory as a volume to the comtainer, set the working directory to the volume, and run the command `gcc -o myapp myapp.c` which will tell gcc to compile the code in myapp.c and output the executable to myapp. Alternatively, if you have a make file, you can instead run the make command inside your container.
|
||||
|
||||
docker run --rm -v "$(pwd)":/usr/src/myapp -w /usr/src/myapp make
|
||||
docker run --rm -v "$(pwd)":/usr/src/myapp -w /usr/src/myapp gcc make
|
||||
|
|
|
|||
|
|
@ -12,13 +12,13 @@ For this image, the most straight-forward use is to use a gcc container as both
|
|||
FROM gcc
|
||||
ADD . /usr/src/myapp
|
||||
WORKDIR /usr/src/myapp
|
||||
RUN gcc -o executable main.c
|
||||
CMD ["./executable"]
|
||||
RUN gcc -o myapp main.c
|
||||
CMD ["./myapp"]
|
||||
|
||||
Then run the commands to build and run the docker image.
|
||||
|
||||
docker build -t my-gcc-app .
|
||||
docker run -it --rm --name my-running-app my-gcc-app ./myapp
|
||||
docker run -it --rm --name my-running-app my-gcc-app
|
||||
|
||||
## Compile your app inside the docker container.
|
||||
|
||||
|
|
@ -28,7 +28,7 @@ It is not always appropriate to run your app inside a container. In instances wh
|
|||
|
||||
This will add your current directory as a volume to the comtainer, set the working directory to the volume, and run the command `gcc -o myapp myapp.c` which will tell gcc to compile the code in myapp.c and output the executable to myapp. Alternatively, if you have a make file, you can instead run the make command inside your container.
|
||||
|
||||
docker run --rm -v "$(pwd)":/usr/src/myapp -w /usr/src/myapp make
|
||||
docker run --rm -v "$(pwd)":/usr/src/myapp -w /usr/src/myapp gcc make
|
||||
|
||||
# Issues and Contributing
|
||||
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ For this image, the most straight-forward use is to use a golang container as bo
|
|||
Then run and build the docker image.
|
||||
|
||||
docker build -t my-golang-app
|
||||
docker run -it --rm --name my-running-app my-golang-app ./myapp
|
||||
docker run -it --rm --name my-running-app my-golang-app
|
||||
|
||||
## Compile your app inside the docker container.
|
||||
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ For this image, the most straight-forward use is to use a golang container as bo
|
|||
Then run and build the docker image.
|
||||
|
||||
docker build -t my-golang-app
|
||||
docker run -it --rm --name my-running-app my-golang-app ./myapp
|
||||
docker run -it --rm --name my-running-app my-golang-app
|
||||
|
||||
## Compile your app inside the docker container.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue