postgresql container in CodeReadyWorkspace operator can't work behind proxy

Open
#418 1 comment 0 reactions 1 assignee View on GitHub

@phracek is already working on this.

Since Feb 22, 2023.

Assessment

This issue has not been assessed yet.

Description

The OpenShift Container Platform version:

Client Version: 4.6.6
Server Version: 4.6.8
Kubernetes Version: v1.19.0+7070803

The Red Hat CodeReady Workspaces version: 2.10.1
The image used for postgresql container : registry.redhat.io/rhel8/postgresql-96@sha256:33643fb4cafffacb277982c6098b561aa80c06210e77d2badebef405ee953e43

The log of postgresql container:

The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale "en_US.utf8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".

Data page checksums are disabled.

fixing permissions on existing directory /var/lib/pgsql/data/userdata ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default timezone ... Etc/UTC
selecting dynamic shared memory implementation ... posix
creating configuration files ... ok
running bootstrap script ... 



pg_ctl: another server might be running; trying to start server anyway
waiting for server to start........LOG:  redirecting log output to logging collector process
HINT:  Future log output will appear in directory "pg_log".
............


cat pg_log



FATAL:  the database system is starting up
LOG:  could not send data to client: Broken pipe
FATAL:  the database system is starting up
LOG:  database system was interrupted; last known up at 2021-09-02 10:02:05 UTC
FATAL:  the database system is starting up
FATAL:  the database system is starting up
FATAL:  the database system is starting up
FATAL:  the database system is starting up
FATAL:  the database system is starting up

There is proxy configured for the container:


env:
      - name: HTTPS_PROXY
        value: 'http://ip:3128'
      - name: HTTP_PROXY
        value: 'http://ip:3128'
      - name: NO_PROXY
        value: >-
         9.0.0.0/8,.<$domain>,.cluster.local,.svc,10.0.0.0/16,10.128.0.0/14,127.0.0.1,172.30.0.0/16,192.168.20.0/24,localhost,api-int.<$domain>,etcd-0.<$domain>,etcd-1.<$domain>,etcd-2.<$domain>

Expect help :
let the postgresql container running. I don’t know why the pg_ctl start failed or why the postgresql server not running in this container.

Dominant language
PLpgSQL
Stars
178
Forks
220
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sclorg/postgresql-container

All issues in sclorg/postgresql-container

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.