#Trying to build a pipeline for creating a container with a webapp

1 messages · Page 1 of 1 (latest)

dim barn
#

Hey.
I am not sure if this is the right place for this question. But I will try anyway, at least to be sure if I have done something wrong

I am currently building a CI CLI process for dotnet programs.
I have a pipeline that generates the wanted container. But for some reason when I try to build an asp.net webapp. it will create the container, but the container is not reachable through a gui, it will however answer to healthcheck endpoint. I assume that it can not find/reach the static files of the wwwroot folder.
However the CLI works fine for an asp.net api. So im not sure if there is some alternative config for building webapps, or i should troubleshoot somewhere else.

dagger_1.png
fickle quartz
#

Hey @dim barn!

In your example I see you are building many containers, but you mention that you are not able to reach an API. Is the API running in the container? (I assume that would be the app ) And in which stage of the code are you indeed starting the container with the API?

dim barn
#

so this is (or should) build multiple containers, one for each architecture i support, "linux/arm64" and "linux/amd64", When running the cli this is a part of, i get a index of images, and the images to my AWS ECR, the code is run in an EKS setup. when i run these images i am able to reach my API's but when i try to do it with a webapp i am not able to reach it.

To be honest im not sure if i my cli is working as intended, and it is in my webapp projects the problem is, or if it is in the CLI.

#

but this part of my pipeline is my weak link knowledge-wise. so that's why im bringing this topic up 🙂

fickle quartz
#

So are you starting the webapp as part of this go script using dagger's services? Or is the problem that when you run the container + image built by dagger (e.g doing docker run) the webapp does not seem to be running?

dim barn
#

the probelm is when i try docker run ect.

#

it seams to be running, but i can not access it (i have assigned ports ect. for it

fickle quartz
#

When you do a local docker run mapping the three ports you have above, none of them work?

dim barn
#

exately, but i have gotten a suspicion around the os packed in the container, at the moment i pack a linux distro, but the asp.net might fail if it is not windows (not something im sure off.)