Avoid ping test for reachability check during image pull from registry

We’re using JFrog’s Artifactory for ours, and I am having issues with pulling in images to use. I can pull them in with no issue using the docker CLI program, but the Concourse-CI Worker, I believe Garden, isn’t able to pull the images in. I guess this is because it uses ping to check if the registry is reachable, where ping is disabled in my registry end. Is there a way to configure garden not to use ping?

   jobs:
- name: processor
  plan:
  - config:
      image_resource:
        source:
          repository: artifactory.ad.company.com:443/docker/busybox
        type: docker-image
      platform: linux
      run:
        args:
        - hello world
        path: echo
    task: processor-task6

And I get the following error:

resource script '/opt/resource/check []' failed: exit status 1

stderr:
failed to ping registry: 2 error(s) occurred:

* **ping** https: Get "https://artifactory.ad.company.com:443/v2/": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

As you can see, ping to my artifactory is disabled for security reasons
$ ping artifactory.ad.company.com
PING artifactory.ad.company.com (...) 56(84) bytes of data.

    --- artifactory.ad.company.com ping statistics ---
    14 packets transmitted, 0 received, 100% packet loss, time 13284ms

And docker pull from CLI works fine. Is there a way for concourse to pull from image registry without using ping to reach reachability?