You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After cloning the project and ensuring all containers are successfully running on Docker Desktop, attempts to access the service at local.altinn.cloud result in a 404 Not Found response. This issue persists even after verifying container statuses and network configurations within Docker Desktop.
Steps To Reproduce
Clone the repository from GitHub.
Start all containers using Docker Desktop.
Verify all containers are running without errors.
Navigate to http://local.altinn.cloud in a web browser.
Additional Information
No modifications were made to the Docker configurations or the project's source code after cloning.
Network settings within Docker Desktop appear to be configured correctly, with no obvious conflicts or misconfigurations.
Other services running on Docker Desktop (if any) are functioning normally.
The issue persists even when switching to Rancher Desktop, indicating that the problem is not specific to Docker Desktop.
All necessary ports appear to be open and not in conflict with other services.
The text was updated successfully, but these errors were encountered:
Description of the bug
After cloning the project and ensuring all containers are successfully running on Docker Desktop, attempts to access the service at local.altinn.cloud result in a 404 Not Found response. This issue persists even after verifying container statuses and network configurations within Docker Desktop.
Steps To Reproduce
Clone the repository from GitHub.
Start all containers using Docker Desktop.
Verify all containers are running without errors.
Navigate to http://local.altinn.cloud in a web browser.
Additional Information
No modifications were made to the Docker configurations or the project's source code after cloning.
Network settings within Docker Desktop appear to be configured correctly, with no obvious conflicts or misconfigurations.
Other services running on Docker Desktop (if any) are functioning normally.
The issue persists even when switching to Rancher Desktop, indicating that the problem is not specific to Docker Desktop.
All necessary ports appear to be open and not in conflict with other services.
The text was updated successfully, but these errors were encountered: