Issue #6628: nginx config broken in Pulp in a Container - Container Support - Pulp

Actions

Send by e-mail Copy link

Issue #6628

closed

nginx config broken in Pulp in a Container

Added by bmclaugh over 4 years ago. Updated over 4 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

fao89

Sprint/Milestone:

1.4.0

Start date:

Due date:

Estimated time:

Severity:

2. Medium

Platform Release:

OS:

Triaged:

Yes

Groomed:

Sprint Candidate:

Tags:

Sprint:

Sprint 72

Quarter:

Description

When using Pulp in a Container [1] I experienced issues with getting 404's when attempting to create a token as well as attempting to pull an image via Podman.

[1] https://pulpproject.org/2020/03/15/pulp-fedora31-single-container/

Files

Download all files

pulp-token-404.txt (1.61 KB) pulp-token-404.txt		bmclaugh, 05/01/2020 07:57 PM
pulp-registry-404.txt (2.23 KB) pulp-registry-404.txt		bmclaugh, 05/01/2020 07:57 PM

Actions

Copy link

Updated by fao89 over 4 years ago

Triaged changed from No to Yes
Sprint set to Sprint 72

Actions

Copy link

Updated by dkliban@redhat.com over 4 years ago

This issue can be worked around by exposing the content app directly (without going through nginx).

$ mkdir settings pulp_storage pgsql containers
$ echo "CONTENT_ORIGIN='$(hostname):8081'
ANSIBLE_API_HOSTNAME='http://$(hostname):8080'
ANSIBLE_CONTENT_HOSTNAME='http://$(hostname):8080/pulp/content'
TOKEN_AUTH_DISABLED=True" >> settings/settings.py

$ podman run --detach \
             --publish 8080:80 \
             --publish 8081:24816 \
             --name pulp \
             --volume ./settings:/etc/pulp:Z \
             --volume ./pulp_storage:/var/lib/pulp:Z \
             --volume ./pgsql:/var/lib/pgsql:Z \
             --volume ./containers:/var/lib/containers:Z \
             --device /dev/fuse \
             pulp/pulp-fedora31

Actions

Copy link