Upgrade to latest Docker Desktop for Windows: Docker is continuously releasing new versions of Docker Desktop for Windows with bug fixes and improvements. Restart PC: A system reboot can solve some problems. See the Sitecore Docker cheat sheet for more details. This is a good daily habit to get into, at minimum, to free up disk space: docker system prune Prune Docker resources: If you have not done so recently, clean up unused Docker resources. docker-compose down), then delete files in the mounted folders manually or with a clean script (see the clean.ps1 examples in the the Docker Examples repository). The default Sitecore configuration enables this for the mssql and solr services. You can restart with the Docker item (the whale icon) in the Windows system tray.Ĭlean mapped volume data: If your containers use mapped volumes for persistent storage, your issue can be come from stale data in these folders. Restart Docker Desktop: Restarting the Docker Desktop often resolves an issue.
The Docker engine (daemon) logs are at C:\Users\%USERNAME%\AppData\Local\Docker. It is helpful to bind mount the Sitecore log folder, as seen in the Docker Examples repository: cm: You can add them to the LogMonitor config ( c:\LogMonitor\LogMonitorConfig.json), but this might result in excessive output. You can also view logs in the Docker Desktop (Dashboard) and with the other tools listed above.įor Sitecore CM and CD images, not all built-in Sitecore log files stream by default. For accessing container logs, see the Sitecore Docker cheat sheet. Depending on the issue, check the logs of a container or the engine logs. Check the logs: The logs are the first place to look.
0 kommentar(er)
