Update base docker image guide

docs/actors/development/base_docker_images.md

@@ -8,23 +8,16 @@ paths:
 
 # [](#base-docker-images) Base Docker images
 
-Apify provides the following Docker images that can be used as a base for user actors:
-
-* **Node.js 12 on Alpine Linux** ([apify/actor-node-basic](https://hub.docker.com/r/apify/actor-node-basic/)) - slim and efficient image, contains only the most elementary tools.
-<br/>
-Note that Puppeteer is not available in this image.
-* **Node.js 12 + Chrome on Debian** ([apify/actor-node-chrome](https://hub.docker.com/r/apify/actor-node-chrome/)) - larger image with the Chromium and Google Chrome browsers and the
-    [puppeteer](https://www.npmjs.com/package/puppeteer) NPM package bundled.
-    With this image, you can use the [`Apify.launchPuppeteer()`](https://sdk.apify.com/docs/api/apify#apifylaunchpuppeteeroptions) function.
-    <br/>
-    Note that Chrome requires quite a lot of resources, therefore the actor should run with at least 1024 MB of memory.
-* **Node.js 12 + Chrome + Xvfb on Debian** ([apify/actor-node-chrome-xvfb](https://hub.docker.com/r/apify/actor-node-chrome-xvfb/)) - extends `apify/actor-node-chrome` with X virtual framebuffer ([Xvfb](https://www.x.org/archive/X11R7.6/doc/man/man1/Xvfb.1.xhtml)) in order to support non-headless browsing.
-    <br/>
-    Note that with this image the [`Apify.launchPuppeteer()`](https://sdk.apify.com/docs/api/apify#apifylaunchpuppeteeroptions) function opens non-headless Chrome by default.
-* **[DEPRECATED] Node.js 10 + Puppeteer on Debian** ([apify/actor-node-puppeteer](https://hub.docker.com/r/apify/actor-node-puppeteer/)).
-<br/>
-    This image is deprecated and will be removed in the future. Use the `apify/actor-node-chrome` image instead.
+Apify provides the following Docker images that can be used as a base for user actors. You can read more about them in the [Apify SDK Docker image guide](https://sdk.apify.com/docs/guides/docker-images).
+
+- **Node.js 14 on Alpine Linux** ([`apify/actor-node`](https://hub.docker.com/r/apify/actor-node/)) - slim and efficient image, contains only the most elementary tools. Note that headless browsers (Puppeteer, Playwright) are not available in this image.
+
+- **Node.js 14 + Puppeteer + Chrome on Debian** ([`apify/actor-node-puppeteer-chrome`](https://hub.docker.com/r/apify/actor-node-puppeteer-chrome/)) - larger image with the Chromium and Google Chrome browsers and the [`puppeteer`](https://github.com/puppeteer/puppeteer) library bundled. With this image, you can use the [`Apify.launchPuppeteer()`](https://sdk.apify.com/docs/api/apify#launchpuppeteer) function and [`PuppeteerCrawler`](https://sdk.apify.com/docs/api/puppeteer-crawler). Note that Chrome requires quite a lot of resources, therefore the actor should run with at least 2048 MB of memory.
+
+- **Node.js 14 + Playwright + Chrome on Debian**  ([`apify/actor-node-playwright-chrome`](https://hub.docker.com/r/apify/actor-node-playwright-chrome/)) - similar to the `apify/actor-node-puppeteer-chrome` image, but it comes preinstalled the [`playwright`](https://github.com/microsoft/playwright) automation library instead of Puppeteer. With this image, you can use the [`Apify.launchPlaywright()`](https://sdk.apify.com/docs/api/apify#launchplaywright) function and [`PlaywrightCrawler`](https://sdk.apify.com/docs/api/playwright-crawler). This image also comes with a `firefox` and `webkit` version.
+
+For a full list of available images, [see the Apify SDK Docker image guide](https://sdk.apify.com/docs/guides/docker-images). Note that some images available in the Apify UI can be marked as deprecated. This means that they should no longer be used for new projects and old projects are encouraged to migrate to one of the non-deprecated images.
 
 All images come in two versions: the **latest** tag corresponds to the stable version and **beta** to images where we test new features. Use the beta version at your own risk.
 
-Note that all Apify Docker images are pre-cached on Apify servers in order to speed-up the actor builds and runs. The source code used to generate the images is available in the [apify-actor-docker](https://github.com/apifytech/apify-actor-docker) GitHub repository.
+Note that all Apify Docker images are pre-cached on Apify servers in order to speed up the actor builds and runs. The source code used to generate the images is available in the [apify-actor-docker](https://github.com/apifytech/apify-actor-docker) GitHub repository.