-
Notifications
You must be signed in to change notification settings - Fork 55
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
Single-process image: pulp-api container does not serve static files / assets #614
Comments
That comment may be wrong. If I remember correctly, the static file are copied to the nginx (pulp-web) container and served from there. Edit: |
We can confirm this issue exists. It might be an issue in pulpcore (because we use the whitenoise app to serve static content). |
It turns out it was a configuration mistake on my side. Somehow I did set
instead of
Now with the correct path the API container is serving the static files as expected. Sorry for the noise. So from my side the issue can be closed. I will leave this up to you though due to your comments about being able to confirm this (or another?) issue. Not sure if it is just a similar mistake with the configuration. |
Hello , @mikedep333 @GeorgFleig @mdellweg This thread similar to what I am looking for, so I put my question here. I have some home made gpg keys, I'd like to put them as static files on pulp server, so our repo can download them. My pulp instance is run on docker-composer(pulp core 3.49.4, rpm 3.25.2), and I have two api instance:
the My question is:
I check inside one compose-pulp_api-1 conainer, it has something under /var/lib/operator:
If there is some example to share? Sorry for the naive questions. Thanks in advance ! |
Version
pulp/pulp-minimal:3.49.0
Describe the bug
According to the nginx config (https://github.com/pulp/pulp-oci-images/blob/latest/images/compose/assets/nginx/nginx.conf.template) the static files are supposed to be served by the API container:
However the API container is not serving them when I browse the API using the browser. Access log from the API container and nginx:
Does this need to be activated first? Or are the assets served on another path?
To Reproduce
Steps to reproduce the behavior:
Use docker-compose or another tool to set up single-process images: https://github.com/pulp/pulp-oci-images/tree/latest/images/compose
Expected behavior
API container serves static files.
Additional context
Add any other context about the problem here. Please provide links to any previous discussions via Discourse or Bugzilla.
The text was updated successfully, but these errors were encountered: