Fixing The Remote Name Could Not Be Resolved "Rendering" Error In Sitecore Docker

July 27, 2022

By Anju Thomas

Fix The Remote Name Could Not Be Resolved "Rendering" Error In Experience Editor Sitecore Docker

The Remote Name Could Not Be Resolved "Rendering" Error In Sitecore Docker

This experience editor issue could be related with the rendering container. So first we will have to check whether our rendering container is up and running. If it's stopped, try restarting the container and wait for the container to start. If it exits and the log shows the below error:

Image Rendering Log In Sitecore Docker

If faced with the above log error:

1. Stop the running containers using docker-compose down.

2. Delete the images of rendering and nodejs. through docker desktop.

Removing images in Docker.

3. Run docker-compose up.

Hopefully the rendering container will be up and running and the experience editor is back!

Anju Headshot

Anju Thomas

Sitecore Web Developer

Anju is a Sitecore Developer with a Bachelor's Degree in Computer Science and over 4 years of experience in Sitecore development. She loves solving Sudoku puzzles, watching movies, eating delicious food and exploring the world.

Second CTA Ogilvy's Legacy

Today, David Ogilvy's influence can still be felt in the world of advertising.

Ogilvy's Influence Example
Emphasis on research Market research is a crucial part of any successful advertising campaign
Focus on headlines A strong headline can make the difference between an ad that is noticed and one that is ignored
Use of visuals Compelling images and graphics are essential for capturing audience attention