docker-nginx | Provides base OS , patches and stable nginx

I'm trying to deploy containerized NGINX server on an AWS EC2 instance to share a directory content over HTTP. I'm using helm command to deploy the container:

I have a need to run a script when my container starts up. (My script creates a json file from the passed in deployment environment variables for my SPA app to use as configuration.) My container is based on the Nginx container.

But a Dockerfile does not allow for more than one ENTRYPOINT and the Nginx container already has one (that I assume I need to keep in there so it will work right.)

I found this question: Docker multiple entrypoints. It's accepted answer suggests that I use Supervisor to accomplish what I need. I was ready to try that out, but one of the alternate answers just uses a script (which was my plan before I saw this answer). In the comments, this solution (of using a script) has a concern raised. It says:

Supervisor is arguably better, since it can restart your processes if they die, has configurable logging options, can receive commands remotely over RPC, etc.

The reference here to "it can restart your processes if they die" concerns me a bit. I am not sure what that means. I don't want my script to be re-run once it is done. (It creates the json file at container startup and is not needed after that.)

Will supervisor cause my script to be re-run over and over?

Or am I fine to use supervisor to run both Nginx's /docker-entrypoint.sh script and my script? Or should I just chain them together and leave supervisor out of it?

I want to set up a websocket server with a reverse proxy. To do so I create a docker-compose with a simple websocket server in python and a nginx reverse proxy.

SETUP:

docker-compose.yml:

I was wanting to setup Let's Encrypt on docker swarm with NGINX and Apache2... The stack was working before ssl. And the classic NOW ITS NOT WORKING! So I have listed my configs and what I'm seeing (Google chrome error: NET::ERR_CERT_INVALID). Let me know if you need any more info from me. Thanks a ton you guys are geniuses I hope that I will have the same knowledge one day :)

SSL labs result (image)

Google Chrome error (image)

nginx.conf:

I try to setup nexus docker repository behind nginx reverse-proxy (with a self-signed SSL certificate). I use this official docker-compose file:

https://github.com/sonatype-nexus-community/docker-nginx-nexus-repository

After installing docker-compose I eventually was able to launch the two containers: nexus3 and nginx with ./nexus.sh. It took me several attempts as I had to change nexus pasword to admin123 and add nexus.scripts.allowCreation=true inside of the docker-nginx-nexus-repository_nexus-repository_1 container (in /nexus-data/etc/nexus.properties) otherwise curl -v -u admin:admin123 --insecure --header 'Content-Type: application/json' 'https://localhost/service/rest/v1/script' -d @nexus-repository/create-docker-proxy.json would fail. At the end I had nexus with docker-proxy repository on http port 5000 pointing on DockerHub.

Furthermore on the host I added:

I've installed docker-ce on RHEL 8 and everything seems to work fine, except that docker containers do not have any network access. I have firewalld service disabled and selinux in permissive mode. Example, I create a container running Alpine with the following command:

docker run -it alpine /bin/sh

Inside the container ifconfig returns:

Good morning everyone,

I have an issue and it's been a month now (seriously) I try to fix it. Here it is: My stack is Symfony Nginx Vue.js.

My project structure :

The api folder is the API code in PHP/Symfony4.4 The back folder is the admin panel in Vue.JS

Both of them are (git) submodules.

My concern is on the Vuejs session. To access the app, we need to log in. In dev mode, everything works fine but not in production mode! Actually, when I submit the form; I have a 405 Not Allowed error

I have no idea on what is happening. So here are my project confs.

1. docker-compose.yml

I have been following a blog for setting up Nginx with SSL from https://blog.harveydelaney.com/hosting-websites-using-docker-nginx/

The article refers to a docker-compose.yml file that doesn't have a version specified at the beginning, but I assume it's at least version 2 as it does have a reference to volumes_from setting within it. This volumes_from is no longer supported in version 3.

Could someone please help migrate the following file to version 3? I am new to the docker / docker-compose / K8s world.

I'm trying to find simple documentation on running certbot in a docker-container, but all I can find is complicated guides w/ running certbot + webserver etc. The official page is kinda useless... https://hub.docker.com/r/certbot/certbot/ .I already have webserver separate from my websites and I want to run certbot on it's own as well.

Can anybody give me some guidance on how I could generate certificates for mysite.com with a webroot of /opt/mysite/html.

As I already have services on port 443 and 80 I was thinking of using the "host-network" if needed for certbot, but I don't really understand why it needs access to 443 when my website is served over 443 already.

I have found something like so to generate a certbot container, but I have no idea how to "use it" or tell it to generate a cert for my site.

Eg: