We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It seems like Apigee user id in the Docker image has been updated from 100 to 101 in the following commit: d7d88a8
RUN addgroup --system --gid 101 apigee && \ adduser --shell /bin/bash --uid 101 --system --ingroup apigee --home /opt/apigee apigee
However, the Kubernetes manifest file still refers this value as 100: https://github.com/apigee-internal/microgateway/blob/v3.1.3/kubernetes/edgemicroctl/install/kubernetes/edgemicro-sidecar-injector-configmap-release.yaml#L30
containers: - name: edge-microgateway image: gcr.io/apigee-microgateway/edgemicro:latest securityContext: runAsNonRoot: true runAsUser: 100 runAsGroup: 101
As a result, ${APIGEE_ROOT}/.edgemicro/$EDGEMICRO_ORG-$EDGEMICRO_ENV-config.yaml file does not get created in the container startup.
The text was updated successfully, but these errors were encountered:
Update runAs user to 101
6784461
#285
837f27b
No branches or pull requests
It seems like Apigee user id in the Docker image has been updated from 100 to 101 in the following commit: d7d88a8
However, the Kubernetes manifest file still refers this value as 100:
https://github.com/apigee-internal/microgateway/blob/v3.1.3/kubernetes/edgemicroctl/install/kubernetes/edgemicro-sidecar-injector-configmap-release.yaml#L30
As a result, ${APIGEE_ROOT}/.edgemicro/$EDGEMICRO_ORG-$EDGEMICRO_ENV-config.yaml file does not get created in the container startup.
The text was updated successfully, but these errors were encountered: