app-UI | user interface components that may be helpful to web | User Interface library

It's because of the mask. You can replace it with the filled version:

Based on the comments.

The issue is caused by calling localhost api endpoint in on the client side in the browser. This will resolve to localhost on the client machine, not within the ECS tasks. The localhost will work when the API is called from the inside of the ECS task, not from outside of the task.

To call the API endpoint from the client side, regular public IP or public DNS is required, not localhost.

Props are passed as an object, so change

You are seeing this error because it is there to protect users from phishing attack. Check out this kustomize issue.

From kustomize faq: security: file ‘foo’ is not in or below ‘bar:

v2.0 added a security check that prevents kustomizations from reading files outside their own directory root.

This was meant to help protect the person inclined to download kustomization directories from the web and use them without inspection to control their production cluster (see #693, #700, #995 and #998).

Resources (including configmap and secret generators) can still be shared via the recommended best practice of placing them in a directory with their own kustomization file, and referring to this directory as a base from any kustomization that wants to use it. This encourages modularity and relocatability.

To disable this, use v3, and the load_restrictor flag:

I fixed this issue by changing the HOST parameter in webpack.dev.conf.js from const HOST = process.env.HOST to const HOST = '0.0.0.0'. I can now access the frontend after starting the containers with docker-compose up. Now to fix communication between the containers!

Thanks to the sachin's comment and going again through the documentation made me realized that I need AuthorizationPolicy on top of RequestAuthentication:

Reference your stepper and then call the following method at the appropriate time (this implementation assumes you are referencing the stepper from a parent component):

It's a syntax error. No need to specify parameter names when passing arguments into a function.

Try this

According to the docs:

With multi-stage builds, you use multiple FROM statements in your Dockerfile. Each FROM instruction can use a different base, and each of them begins a new stage of the build. You can selectively copy artifacts from one stage to another, leaving behind everything you don’t want in the final image. To show how this works, let’s adapt the Dockerfile from the previous section to use multi-stage builds. https://docs.docker.com/develop/develop-images/multistage-build/

so, pip is not present in the final image, since you are getting FROM nginx:alpine after get python

I think the best solution is to pip install before last FROM, and keep as suggested here: https://pythonspeed.com/articles/multi-stage-docker-python/