I believe j.p.s. was talking about distributing a dockerfile. It's a config file only. No software would be distributed. The dockerfile merely creates the container. But unless there's a direct url which can be used to download the official ADE installer, you'll still be in a situation where the ADE installer will need to be hosted somewhere by someone so that the OS running inside the docker container could consistently access the correct version.
Then you'd have to map shared storage with the host machine where WINE could store its registry (so you didn't have to register that instance of ADE each and every time the container was started), as well as mapping ADE's library location to be shared with the host machine so the downloaded ebooks would persist after downloading.
None of that takes into consideration what needs to happen to even get an ADE-Running-in-WINE-in-a-Linux-Docker-Container in the first place.
It's just not worth the trouble in my opinion. Just fire up a VirtualBox XP guest with ADE installed on it and be done.
EDIT: Also ... Docker has considerable overhead to begin with. If people weren't crazy about a WINE prefix taking a ton of disk space, just wait until you see how much Docker, a basic Linux server image, all the extra software needed to install WINE, and the WINE software needed to run ADE in WINE will take up! Better beef up /var (or configure Docker to store its containers/images elsewhere).