# Dockerfile contains instructions how to build a Docker image that
# will contain all the code and configuration needed to run your actor.
# For a full Dockerfile reference,
# see https://docs.docker.com/engine/reference/builder/

# First, specify the base Docker image. Apify provides the following
# base images for your convenience:
# apify/actor-node-basic (Node.js on Alpine Linux, small and fast)
# apify/actor-node-chrome (Node.js + Chrome on Debian)
# apify/actor-node-chrome-xvfb (Node.js + Chrome + Xvfb on Debian)
# For more information, see https://docs.apify.com/actor/build#base-images
# Note that you can use any other image from Docker Hub.
FROM apify/actor-node-basic

# Second, copy just package.json since it should be the only file
# that affects "npm install" in the next step, to speed up the build
COPY package.json ./

# Install NPM packages, skip optional and development dependencies to
# keep the image small. Avoid logging too much and print the dependency
# tree for debugging
RUN npm --quiet set progress=false \
 &amp;&amp; npm install --only=prod --no-optional \
 &amp;&amp; echo "Installed NPM packages:" \
 &amp;&amp; npm list || true \
 &amp;&amp; echo "Node.js version:" \
 &amp;&amp; node --version \
 &amp;&amp; echo "NPM version:" \
 &amp;&amp; npm --version

# Next, copy the remaining files and directories with the source code.
# Since we do this after NPM install, quick build will be really fast
# for most source file changes.
COPY . ./

# Optionally, specify how to launch the source code of your actor.
# By default, Apify's base Docker images define the CMD instruction
# that runs the Node.js source code using the command specified
# in the "scripts.start" section of the package.json file.
# In short, the instruction looks something like this:
#
# CMD npm start

Dockerfile

# My beautiful actor

Contains a documentation what your actor does and how to use it,
which is then displayed in the app or library. It's always a good
idea to write a good README.md, in a few months not even you
will remember all the details about the actor.

You can use [Markdown](https://guides.github.com/features/mastering-markdown/)
language for rich formatting.

README.md

main.js

{
 "name": "anti-captcha",
 "version": "0.0.1",
 "dependencies": {
 "apify": "^1.0.0",
 "node-fetch": "^2.6.1"
 },
 "scripts": {
 "start": "node main.js"
 },
 "author": "Petr Cermak"
}

package.json

# Dockerfile contains instructions how to build a Docker image that
# will contain all the code and configuration needed to run your actor.
# For a full Dockerfile reference,
# see https://docs.docker.com/engine/reference/builder/

# First, specify the base Docker image. Apify provides the following
# base images for your convenience:
#  apify/actor-node-basic (Node.js on Alpine Linux, small and fast)
#  apify/actor-node-chrome (Node.js + Chrome on Debian)
#  apify/actor-node-chrome-xvfb (Node.js + Chrome + Xvfb on Debian)
# For more information, see https://docs.apify.com/actor/build#base-images
# Note that you can use any other image from Docker Hub.
FROM apify/actor-node-basic

# Second, copy just package.json since it should be the only file
# that affects "npm install" in the next step, to speed up the build
COPY package.json ./

# Install NPM packages, skip optional and development dependencies to
# keep the image small. Avoid logging too much and print the dependency
# tree for debugging
RUN npm --quiet set progress=false \
 && npm install --only=prod --no-optional \
 && echo "Installed NPM packages:" \
 && npm list || true \
 && echo "Node.js version:" \
 && node --version \
 && echo "NPM version:" \
 && npm --version

# Next, copy the remaining files and directories with the source code.
# Since we do this after NPM install, quick build will be really fast
# for most source file changes.
COPY . ./

# Optionally, specify how to launch the source code of your actor.
# By default, Apify's base Docker images define the CMD instruction
# that runs the Node.js source code using the command specified
# in the "scripts.start" section of the package.json file.
# In short, the instruction looks something like this:
#
# CMD npm start


# My beautiful actor

Contains a documentation what your actor does and how to use it,
which is then displayed in the app or library. It's always a good
idea to write a good README.md, in a few months not even you
will remember all the details about the actor.

You can use [Markdown](https://guides.github.com/features/mastering-markdown/)
language for rich formatting.


Apify Store

Marketplace

Enterprise

Compare the options 🤔

Use cases

Success stories

Actors

Storage

Proxy

Integrations

Documentation

Apify SDK

Stack Overflow

Join Marketplace

Help & Support

Ask the community

Blog

About Apify

Contact us

Careers

Become a partner

Affiliate program

Anti Captcha

Build new tools

Order custom tool