TZData | Timezone repository based on IANA/TZDB

~ is a shorthand for $HOME, the user's home directory. In this case this is /root. But as your ls command shows, the repo's directory is in the current directory. If you do pwd, you will see the current directory is not /root. Instead do cd qdomyos-zwift so that it is relative to the current directory.

I think you are running the Docker build on a specific path that need administrator permissions , to resolve that just copy your project to the Desktop for example and try again :

As per my comment above, this seems confused.

You open up with "binary from the PPA are built under a more current version": yes, and that is a feature. If you do not want a current dplyr (via a current r-cran-dplyr) then do not add the PPA by Michael (which you do correctly by following the steps at the README.

The disconnect, if there is one, is that you seem to think that you point to that PPA and somehow get versions matching an arbitrarily picked R version, here your 4.0.4. You cannot, and we never say you can.

What we provide via the CRAN mirror of the other Rutter PPA are

• current versions of R for the various operating systems, i.e. Michael tweeted just yesterday that 4.0.3 is now available off my Debian binaries
• about 5000 additional binaries off CRAN for the LTS release but also generally built with most current R version---which is why the dplyr binary signalled it was built recently under 4.0.4

So in short this is not a time machine mechanism.

(For that you can look into the RSPM builds for which I have a container rocker/r-rspm:20.04 to use RSPM, you could try the date-indexing support they offer. I don't use enable that by default.)

If I misunderstood anything, please add a comment and maybe clarify above. The r-sig-debian list is also available for more follow-up.

Edit: Per the discussion in the comments, we now know better. OP constrained just one package from the set and expected that apt would magically expand. That is not how it happens. Based on some other Dockerfile I wrote, I recommend something along the lines of

The issue was coming from my Procfile. I was passing the folder name (vicsite) instead of the project name(site_server):

web: gunicorn vicsite.wsgi --log-file -

So the correct code to write is:

web: gunicorn site_server.wsgi --log-file -

If you did the original install as pip install psycopg you got the pure Python version. Per Installation instructions Pure Python installation that means you need to have the libpq library installed also. Not sure how you would get that on Windows. I would say the solution is to:

pip uninstall psycopg

then

pip install psycopg[binary]

This will get you the self-contained(all needed libraries) install.

After a few days I was able to find the solution

Firstly, my code needed to be fixed to correctly call the params needed with the proper name

libc6-compat was missing from my alpine image.

The setuptools.setup call in setup.py seems to be missing a packages parameter. So you are distributing an empty Python project without any importable package. You probably need either packages=setuptools.find_packages() or packages=['testing'].

Dot Points:

• include $request_uri in your proxy pass
• provide a resolver in your proxy location block
• declare an entry for your container in Docker's network stack
• use all lower case in your service name

Below is the configuration file I use to reverse proxy through to a Ubiquiti Unifi container. All my certbot is handled off site so I need not consider that here. If you compare our location blocks, the issue will likely become immediately apparent, but I'll explain for clarity's sake.

What you need to look at is your Proxy Pass directive. This is of course where the magic proxying happens. I notice that you have not been including the $request_uri, so any request nginx receives for bound.example.com/testpage1, it will send a request to the upstream apache server for bound.example.com. Of course if you need to include a port, as I have done here 8443, this is the place to do it also.

If you include this variable, it should resolve your problem.

The following does not answer your question, but I thought I would include it also just as some helpful information.

Also, I just want to note that I have included a resolver. The IP address 127.0.0.11 points to Docker's internal DNS resolver. Chances are you won't need to include this, however I did so myself to ensure I didn't get odd problems. Lastly, I'd just like to recommend that you look into upgrading your SSL settings, to ensure that you are safe from attacks from weaker SSL / TLS versions.

I expect that adding the variable $request_uri to your proxy pass directive is all that is required to get your site working.