[jira] [Resolved] (ARTEMIS-3635) Problems with prepare-docker.sh

["Justin Bertram (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARTEMIS-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Bertram resolved ARTEMIS-3635.
-------------------------------------
    Resolution: Information Provided

The first issue should be resolved now given the recent updates to the script.

Regarding the second issue I recommend investigating your proxy/environment. I don't experience this issue and I've not seen any other reports of it either.

> Problems with prepare-docker.sh
> -------------------------------
>
>                 Key: ARTEMIS-3635
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3635
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 2.20.0
>            Reporter: Jonas Taulien
>            Priority: Major
>
> Executing the prepare script on Debian 9 with the command `./prepare-docker.sh --from-release --artemis-version '20.2.0'` leads to the following problems
> # Executing `if [ -z "$(ls -A ${BASE_TMPDIR}/${ARTEMIS_VERSION})" ]` leads to `ls: cannot access '\_TMP\_/artemis/20.2.0': No such file or directory`. Because of that the script fails silently. I propose to use `if [ ! -d "${BASE_TMPDIR}/${ARTEMIS_VERSION})" ]` instead
> # Executing `curl  https://www.apache.org/dyn/closer.cgi/?preferred=true` leads to an error `curl: (60) SSL certificate problem: certificate has expired` on my machine. Maybe this is because of my proxy. Can you maybe add an option to execute curl with the `--insecure` option?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)