Open archaica opened 3 months ago
@archaica Use docker compose up --watch
instead.
Will get the guides fixed.
That yields the same error.
@archaica I suspect this is due to network connectivity problems or interference from a proxy server that's corrupting the certificate chain.
Which Docker Desktop(Mac/Linux/Windows) version are you using? Can you try it once on your laptop outside your company network? If this is your laptop or server, try temporarily disabling firewalls to see if the issue persists. Access the registry server from a different network to rule out network-specific problems.
Also, what happens when you run the npm install
command locally for each of the backend/
and client/
directories? Does it work well?
The docker compose up --watch
worked for me.
Thanks Y. Tazky.
@harigithubac The error message you're seeing indicates that Docker Compose is encountering issues pulling images from Docker Hub due to invalid credentials. This is unexpected, as the images used in the compose file typically don't require login to Docker Hub. Are you using a corporate laptop? If so, ensure you're not restricted by the company's firewall.
That yields the same error.
that must be different error if your running on windows port 80 is reserved change the port in compose.yaml
` proxy: image: traefik:v2.11 command: --providers.docker ports:
When I run the command
docker compose watch
as suggested in the docker documentation here: https://docs.docker.com/guides/getting-started/develop-with-containers/I get the following results
This seems to be to be a root cert issue that should be indigenously solved inside the container?