I am trying to create a docker container for my node.js application. When I run the docker desktop in administrator and Powershell in Administrator I get the following error.
PS C:\Users\User\NodejsWebApp1\NodejsWebApp1> FROM node:12
At line:1 char:1
+ FROM node:12
+ ~~~~
The 'from' keyword is not supported in this version of the language.
+ CategoryInfo : ParserError: (:) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : ReservedKeywordNotAllowed
PS C:\Users\User\NodejsWebApp1\NodejsWebApp1>
PS C:\Users\User\NodejsWebApp1\NodejsWebApp1> # Create app directory
PS C:\Users\User\NodejsWebApp1\NodejsWebApp1> WORKDIR /usr/src/app
WORKDIR : The term 'WORKDIR' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ WORKDIR /usr/src/app
+ ~~~~~~~
+ CategoryInfo : ObjectNotFound: (WORKDIR:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
PS C:\Users\User\NodejsWebApp1\NodejsWebApp1>
PS C:\Users\User\NodejsWebApp1\NodejsWebApp1> # Install app dependencies
PS C:\Users\User\NodejsWebApp1\NodejsWebApp1> # A wildcard is used to ensure both package.json AND package-lock.json are copied
PS C:\Users\User\NodejsWebApp1\NodejsWebApp1> # where available (npm#5+)
PS C:\Users\User\NodejsWebApp1\NodejsWebApp1> COPY package*.json ./
COPY : Cannot overwrite the item
C:\Users\User\NodejsWebApp1\NodejsWebApp1\package-lock.json with itself.
At line:1 char:1
+ COPY package*.json ./
+ ~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : WriteError: (C:\Users\User\N...ckage-lock.json:String)
[Copy-Item], IOException
+ FullyQualifiedErrorId :
CopyError,Microsoft.PowerShell.Commands.CopyItemCommand
COPY : Cannot overwrite the item
C:\Users\User\NodejsWebApp1\NodejsWebApp1\package.json with itself.
At line:1 char:1
+ COPY package*.json ./
+ ~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : WriteError: (C:\Users\User\N...p1\package.json:String) [Copy-Item], IOException
+ FullyQualifiedErrorId :
CopyError,Microsoft.PowerShell.Commands.CopyItemCommand
PS C:\Users\User\NodejsWebApp1\NodejsWebApp1>
PS C:\Users\User\NodejsWebApp1\NodejsWebApp1> RUN npm install
RUN : The term 'RUN' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:1 char:1
+ RUN npm install
+ ~~~
+ CategoryInfo : ObjectNotFound: (RUN:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
PS C:\Users\User\NodejsWebApp1\NodejsWebApp1> # If you are building your code
for production
PS C:\Users\User\NodejsWebApp1\NodejsWebApp1> # RUN npm ci --only=production
PS C:\Users\User\NodejsWebApp1\NodejsWebApp1>
PS C:\Users\User\NodejsWebApp1\NodejsWebApp1> # Bundle app source
PS C:\Users\User\NodejsWebApp1\NodejsWebApp1> COPY . .
COPY : Cannot overwrite the item C:\Users\User\NodejsWebApp1\NodejsWebApp1 with
itself.
At line:1 char:1
+ COPY . .
+ ~~~~~~~~
+ CategoryInfo : WriteError: (C:\Users\User\N...1\NodejsWebApp1:String)
[Copy-Item], IOException
+ FullyQualifiedErrorId :
CopyError,Microsoft.PowerShell.Commands.CopyItemCommand
PS C:\Users\User\NodejsWebApp1\NodejsWebApp1>
PS C:\Users\User\NodejsWebApp1\NodejsWebApp1> EXPOSE 3000
EXPOSE : The term 'EXPOSE' is not recognized as the name of a cmdlet, function,
script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path
is correct and try again.
At line:1 char:1
+ EXPOSE 3000
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: (EXPOSE:String) [],
CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
PS C:\Users\User\NodejsWebApp1\NodejsWebApp1> CMD [ "node", "server.js"
]ect.:ect.:
Sorry about the mess of error, but that is what it was printing out!
The command I was running was
docker build -t name .
This is my DockerFile
FROM node:12
# Create app directory
WORKDIR /usr/src/app
# Install app dependencies
# A wildcard is used to ensure both package.json AND package-lock.json are copied
# where available (npm#5+)
COPY package*.json ./
RUN npm install
# Bundle app source
COPY . .
EXPOSE 3000
CMD [ "node", "server.js" ]
Should I maybe try doing this in Linux as I am currently running Windows 10, would this be a greater option.
Many thanks. Jeff
Related
browser-sync start --server --directory --files "*"
browser-sync : File C:\Users\Sumithra\AppData\Roaming\npm\browser-sync.ps1 cannot be loaded because running scripts is
disabled on this system. For more information, see about_Execution_Policies at
https:/go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:1
+ browser-sync start --server --directory --files "*"
+ ~~~~~~~~~~~~
+ CategoryInfo : SecurityError: (:) [], PSSecurityException
+ FullyQualifiedErrorId : UnauthorizedAccess
what to do ?
please anyone help me for this
I have found a docker image with msbuild and nuget installed. I want to use msbuild to build my .NET framework project, but it returns the following error:
$ & "$env:MSBUILD_PATH" /p:Configuration=Release /clp:ErrorsOnly
& : The term 'C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe' is not
recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if
a path was included, verify that the path is correct and try again.
At line:1 char:3
+ & "$env:MSBUILD_PATH" /p:Configuration=Release /clp:ErrorsOnly
+ ~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (C:\Program File...Bin\MSBuild.exe:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Here is my yaml file:
.shared_windows_runners:
tags:
- shared-windows
- windows
- windows-1809
variables:
MSBUILD_PATH: 'C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe'
NUGET_PATH: 'C:\Nuget\nuget.exe'
stages:
- build
build:
extends:
- .shared_windows_runners
stage: build
image: compulim/msbuild
script:
- echo "start building"
- '& "$env:MSBUILD_PATH" /p:Configuration=Release /clp:ErrorsOnly'
- '& "$env:MSBUILD_PATH" WebCICD\WebCICD.csproj /p:DeployOnBuild=true /p:Configuration=Release /P:PublishProfile=FolderProfile.pubxml'
- Tree
I found this docker image by googling "docker msbuild image".
I thought the image could let me use the file path to build the project directly. Am I wrong?
Is there anything I am missing?
Thanks
This is my Dockerfile content and it keeps throwing me error in running this statement. Any idea what am I doing wrong. I just want to dump ENV VARS into a file for React build on the container.
FROM node:12
WORKDIR /usr/src/app
COPY . .
RUN printenv | grep REACT_APP_ > client/.env
# RUN ["printenv", "|", "grep", "REACT_APP_", ">", "client/.env"]
RUN npm run setup
RUN npm run build:all
EXPOSE 3005
CMD [ "npm", "run", "start:prod" ]
Error: ERROR: Service '<name>' failed to build: The command 'printenv | grep REACT_APP_ > client/.env' returned a non-zero code: 1
I have spent many hours with no luck. Help appreciated.
So there's a couple things to consider:
Make sure the client dir exists. It doesn't come in the node:12 image by itself
Make sure the env has a variable that will allow the grep REACT_APP_ to find something. If it does not, grep will return 1 and the docker image build will halt. 1 is normal return code when grep finds nothing, so it's not an error (and thus nothing more is printed). But the docker build treats it as an error since it's nonzero, and thus the build stops.
Also to read on EXIT CODES on man grep page,
EXIT STATUS Normally the exit status is 0 if a line is selected, 1 if
no lines were selected, and 2 if an error occurred.
Here's a test I did that passes (slightly modified, just based on the considerations above):
FROM node:12
WORKDIR /usr/src/app
COPY . .
RUN mkdir client
ENV REACT_APP_1 1
RUN printenv | grep REACT_APP_ > client/.env
RUN cat client/.env
The output I get is this:
$ docker build -t test .
Sending build context to Docker daemon 2.048kB
Step 1/7 : FROM node:12
---> 28faf336034d
Step 2/7 : WORKDIR /usr/src/app
---> Running in 753293fa6257
Removing intermediate container 753293fa6257
---> 3a04798b1b9f
Step 3/7 : COPY . .
---> 3dd0d465a6e2
Step 4/7 : RUN mkdir client
---> Running in d513df2a0a34
Removing intermediate container d513df2a0a34
---> d46aa5200ae7
Step 5/7 : ENV REACT_APP_1 1
---> Running in af81940a90fb
Removing intermediate container af81940a90fb
---> 6169ad694a4d
Step 6/7 : RUN printenv | grep REACT_APP_ > client/.env
---> Running in 365020eeb2e5
Removing intermediate container 365020eeb2e5
---> b6ef574c48c8
Step 7/7 : RUN cat client/.env
---> Running in a6a69d6ba6c2
REACT_APP_1=1
Removing intermediate container a6a69d6ba6c2
---> 0814306133f0
Successfully built 0814306133f0
Successfully tagged test:latest
I need help in debugging this image build:
My dockerfile is :
FROM node:latest
WORKDIR /app
COPY . .
ENV PORT = 3000
RUN npm install
EXPOSE $PORT
ENTRYPOINT [ "node", "app.js" ]
and when I run sudo docker build -t uddeshya/node1 . to build the image, the log shows the following:
Sending build context to Docker daemon 2.009MB
Step 1/7 : FROM node:latest
---> dcda6cd5e439
Step 2/7 : WORKDIR /app
---> Using cache
---> 9450405b180f
Step 3/7 : COPY . .
---> Using cache
---> 91689830af35
Step 4/7 : ENV PORT = 3000
---> Using cache
---> d99d55d0ae81
Step 5/7 : RUN npm install
---> Using cache
---> dac4854ec168
Step 6/7 : EXPOSE $PORT
Invalid containerPort: =
The error point is at "EXPOSE $PORT", how do I fix this?
The syntax of ENV should be
ENV PORT=3000
That is the build throw error as it receives = because of spaces.
Step 3/6 : ENV PORT = 3000
---> Using cache
---> 8edc1281a96c
Step 4/6 : RUN echo ${PORT}
---> Running in 090a69369847
= 3000
without spaces it should be
Step 3/6 : ENV PORT=3000
---> Using cache
---> dc29398a0ca6
Step 4/6 : RUN echo ${PORT}
---> Running in 9fc5d9b07342
3000
then yon can verify
docker inspect your_image
you can see
"ExposedPorts": {
"3000/tcp": {}
}
I was getting started with Docker, created couple of tiny Express(NodeJS) services.
Plan is to run the microservices inside Docker containers and then establish a inter-communication between them using Docker Compose service names.
Here is the Github repo of this simple project. Am able to build images with below commands :
cd books
docker build -t node-micro/books .
cd auth
docker build -t node-micro/auth .
Commands to start containers :
docker run -d -p 6677:6677 node-micro/auth
docker run -d -p 7766:7766 node-micro/books
But when i hit below URL's there is no response, which was working fine couple of day's before :
http://localhost:6677/
http://localhost:7766/
And have no clue what's happening with docker compose. No luck on accessing same URL's as mentioned above after stoping all containers, delete all images & ran this command :
docker-compose up -d
Need some help on bringing up the containers individually and also through docker-compose.
I can see in each of your micro-service, your application is running on ports 3000 in the container but you are exposing 7766 and 6677 in your docker-compose.yml
Please check the below docker-compose.yml
version: '3'
services:
books:
build: './books'
ports:
- "7766:3000"
depends_on:
- auth
auth:
build: './auth'
ports:
- "6677:3005"
and then run the below command
docker-compose up --build
--build will build the images as well.
Then, you should be able to access the service
http://localhost:6677/
http://localhost:7766/
Output
docker-compose up --build
Creating network "node_microservices_default" with the default driver
Building auth
Step 1/7 : FROM node:10-alpine
---> 0aa7bb41deca
Step 2/7 : WORKDIR /usr
---> Running in a1dc67b70538
Removing intermediate container a1dc67b70538
---> 5fc74fc80a14
Step 3/7 : COPY package*.json ./
---> 454f1b7aba87
Step 4/7 : RUN npm install
---> Running in a24eea8b79d4
npm WARN auth#1.0.0 No description
npm WARN auth#1.0.0 No repository field.
added 50 packages from 37 contributors and audited 50 packages in 8.58s
found 0 vulnerabilities
Removing intermediate container a24eea8b79d4
---> 31b31ff4516e
Step 5/7 : COPY . .
---> 1eeaa8e70300
Step 6/7 : EXPOSE 3000
---> Running in fc798167dbcd
Removing intermediate container fc798167dbcd
---> 4d964d25c099
Step 7/7 : CMD ["npm", "start"]
---> Running in 3c28d92f9ef6
Removing intermediate container 3c28d92f9ef6
---> 514f68d11d7c
Successfully built 514f68d11d7c
Successfully tagged node_microservices_auth:latest
Building books
Step 1/7 : FROM node:10-alpine
---> 0aa7bb41deca
Step 2/7 : WORKDIR /usr
---> Using cache
---> 5fc74fc80a14
Step 3/7 : COPY package*.json ./
---> 56addb6c75a5
Step 4/7 : RUN npm install
---> Running in 4864fb7a171c
npm WARN books#1.0.0 No description
npm WARN books#1.0.0 No repository field.
added 50 packages from 37 contributors and audited 50 packages in 5.111s
found 0 vulnerabilities
Removing intermediate container 4864fb7a171c
---> 82bb2cd54357
Step 5/7 : COPY . .
---> 12893a93e82e
Step 6/7 : EXPOSE 3000
---> Running in 1301e29dbd52
Removing intermediate container 1301e29dbd52
---> c26948ebcb3b
Step 7/7 : CMD ["npm", "start"]
---> Running in db948866a121
Removing intermediate container db948866a121
---> 703b901d7bc4
Successfully built 703b901d7bc4
Successfully tagged node_microservices_books:latest
Creating node_microservices_auth_1 ... done
Creating node_microservices_books_1 ... done
Attaching to node_microservices_auth_1, node_microservices_books_1
auth_1 |
auth_1 | > auth#1.0.0 start /usr
auth_1 | > node index.js
auth_1 |
auth_1 | Running on port 3005
auth_1 | --------------------------
books_1 |
books_1 | > books#1.0.0 start /usr
books_1 | > node index.js
books_1 |
books_1 | Running on port 3000
books_1 | --------------------------
You are exposing from both Dockerfiles the port 3000. Replace the port for each microservice in docker-compose.yml file.
- "7766:3000"
- "6677:3000"
The mapping for ports is wrong. In both Dockerfile you are exposing the port 3000.
So you must to map the ports 6677 and 7766 to the exposed port on the Dockerfile.
To fix this, on your docker-compose.yml you must to config ports like this:
version: '3'
services:
books:
build: './books'
ports:
- "7766:3000"
depends_on:
- auth
auth:
build: './auth'
ports:
- "6677:3000"