FTP | An client FTP in Java | FTP library

As you already figured out in the comments, the tricky part about FTP passive mode is that the server uses another port (not 21) for communication. In the docker image you're using, it's a port from the 21000-21010 range by default. So you need to publish (expose) these additional container ports. In docker run command you used -p 21000-21010:21000-21010 for that.

However, Testcontainers library is designed to publish to random host ports to avoid the problem, when a desired fixed port (or a range of ports) is already occupied on the host side. In case of FTP passive mode random ports on the host side cause problems, because afaik you can't instruct the ftp client to override the port, which FTP server returned for the passive mode. You'd need something like ftpClient.connect("localhost", ftp.getMappedPort(PORT)); but for passive mode ports as well.

Therefore the only solution I see here is to use a FixedHostPortContainer. Even though it's marked as deprecated and not recommended to use because of the mentioned issues with occupied ports, I think this is a valid use case for it here. FixedHostPortGenericContainer allows to publish fixed ports on the host side. Something like:

Try env ARCHFLAGS="-arch x86_64"

(that works for me for other Python-related tools, I don't use pyenv myself).

Rationale: modern macOS supports 2 architectures: intel (x86_64) and m1 (arm-something). Compiling for only one architecture is easier.

Try with hirsute :

The "/AdvancedCalender/Calenders/Versions" is a relative URI, so you need to tag is like that:

From Python3.10, OpenSSL 1.1.1 or newer is required.

(Ref: PEP 644, Python3.10 release)

I have tried changing some of your code like below and worked.

delete: openssl-devel

add: openssl11 openssl11-devel.

The message

It's because a breaking change in the globalizations APIs in .NET 5. You can choose one of the following approaches

1. Use StringComparison.Ordinal or OrdinalIgnoreCase
2. Use NLS instead of ICU, with one of the following ways:

• In the project file:

Is this giving you what you want?

TL;DR; The stable images on docker hub have not yet been regenerated for Debian 11, but the security repo changed layout. The next rebuild of the stable docker image should be Debian 11 based and that should fix the problem.

--- Details ---

It seems the stable and stable-slim tags are currently a bit broken at docker hub.

For Debian 10 and older, the repo uses the subdirectory structure {RELEASE}/updates to contain the security updates;