-
Notifications
You must be signed in to change notification settings - Fork 261
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker-Compose & PS build errors - can't bring up the solution #582
Comments
Your docker-compose context is defined in the ./build/aspnet-core/services/Publish/ subdirectory, and the build script build-aspnetcore-release.ps1 output is in the /aspnet-core/services/Publish/ subdirectory |
Sorry but I don't understand what you are referring to. The build script build-aspnetcore-release.ps1 is run from the ./build directory and outputs therefore to ./build/aspnet-core/services/Publish/. This is exactly the path the docker-compose references to. I also have not changed the files in terms of the paths. They are the original ones provided by you. When I run docker by So I'm assuming this has to do with Redis. It's not present in your docker-compose, so not sure if it every worked for you. I have it within my docker-compose version shown above and it's up and running but I assume the microservices are not pointed into the right location (ip:port). |
As you can see from the error stack, the application did not find the redis configuration in appsettings.json or appsettings.{env}.json when it started, please check |
build-aspnetcore-release.ps1 uses a relative path to build, so the output directory is not under the build directory |
Thank you, I'm just not able to get it to run. Can you provide a docker-compose which covers all the requirements to run it? Like RabbitMQ, the database, Redis, etc. |
Maybe you need to add the -f docker-compose.configuration, yml? |
No doesn't work. I also had to change the whole references in docker-compose.configuration.yml because the names don't match any longer (i.e., admin-service must be admin-api, etc.). I was hoping you would provide a Docker compatibility but this just doesn't work and is buggy as hell. Not going to play with it any further and trashing plans to use this project. |
I would consider incorporating middleware into docker-compose as well |
#943 once deploy script has been added to this commit, Warning: |
with the GA of aspire,we can use aspire to develop,and generate docker compose yaml or k8s yaml |
Hello,
I have not been able to start your solution yet.
The PS build scripts do not work on my machine. I had to adjust those so it compiles at least.
When bringing up Docker as per your tutorial the services keep restarting. I started adding the ABP framework requirements to docker but has not worked out so far. Could you provide an updated docker-compose with maybe also SQL server set-up already? Would be good to have a "one-line" startup solution. Thank you! Here are my adapted files so far.
JFYI: I also tried the "dotnet new --install LINGYUN.Abp.MicroService.Templates::5.2.0" approach as in your Readme but 5.2.0 is not available yet.
docker-compose.yml:
docker-compose.override.yml:
build-aspnetcore-release.ps1:
build-aspnetcore-common.ps1:
The text was updated successfully, but these errors were encountered: