"/usr/local/bin/docker-entrypoint.sh: line 97: setcap: not found" in docker logs of vault

**Description**

We are encountering an issue when starting a Vault Docker container using the 2.0.3 image.

**Issue**

When the container starts, it immediately fails with the following error:

root@virtplatform:~# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
b1c9e249a3ed XXX.XXX.XXX./hashicorp/vault:2.0.3 "docker-entrypoint.s…" 10 minutes ago Restarting (127) 42 seconds ago vault

**Environment:**
1.Vault image version: 2.0.3
2.Deployment method: Docker container
3.OS: Ubuntu 24.04.3 LTS
4.Docker version: 29.1.3

**Steps to Reproduce:**
1.Pull the 2.0.3 Vault image.
2.Start the container with the existing configuration.
3.Observe that the container fails during startup with the error shown above.

**Expected Behavior**

The Vault container should start successfully without any errors.

**Actual Behavior**

The container fails to start and exits with the error mentioned above.

**Additional Information**
As of now temporary solution is tp that use this variable in docker environment
**SKIP_SETCAP=1**

Please let us know if any additional logs or configuration details are required to help diagnose the issue.

While checking on docker logs and getting following errors
root@:~# docker logs vault
/usr/local/bin/docker-entrypoint.sh: line 97: setcap: not found
/usr/local/bin/docker-entrypoint.sh: line 97: setcap: not found
/usr/local/bin/docker-entrypoint.sh: line 97: setcap: not found
/usr/local/bin/docker-entrypoint.sh: line 97: setcap: not found
/usr/local/bin/docker-entrypoint.sh: line 97: setcap: not found
/usr/local/bin/docker-entrypoint.sh: line 97: setcap: not found
/usr/local/bin/docker-entrypoint.sh: line 97: setcap: not found
/usr/local/bin/docker-entrypoint.sh: line 97: setcap: not found
/usr/local/bin/docker-entrypoint.sh: line 97: setcap: not found
/usr/local/bin/docker-entrypoint.sh: line 97: setcap: not found
/usr/local/bin/docker-entrypoint.sh: line 97: setcap: not found
/usr/local/bin/docker-entrypoint.sh: line 97: setcap: not found
/usr/local/bin/docker-entrypoint.sh: line 97: setcap: not found
/usr/local/bin/docker-entrypoint.sh: line 97: setcap: not found
/usr/local/bin/docker-entrypoint.sh: line 97: setcap: not found
/usr/local/bin/docker-entrypoint.sh: line 97: setcap: not found
/usr/local/bin/docker-entrypoint.sh: line 97: setcap: not found
/usr/local/bin/docker-entrypoint.sh: line 97: setcap: not found
/usr/local/bin/docker-entrypoint.sh: line 97: setcap: not found
/usr/local/bin/docker-entrypoint.sh: line 97: setcap: not found
/usr/local/bin/docker-entrypoint.sh: line 97: setcap: not found
/usr/local/bin/docker-entrypoint.sh: line 97: setcap: not found
/usr/local/bin/docker-entrypoint.sh: line 97: setcap: not found
/usr/local/bin/docker-entrypoint.sh: line 97: setcap: not found

Could you please help us determine how to resolve this issue? We would also like to know whether this is a known issue with the latest 2.0.3 Vault Docker image or if there are any additional configuration changes required to run this version successfully.

If this is a known issue, please let us know if there is a recommended workaround or if using an earlier image version is advised.

Start with /usr/local/bin/docker-entrypoint.sh at line 97 in the Vault 2.0.3 image and compare startup behavior with SKIP_SETCAP=1. Reproduce the failure using the stated Docker and Ubuntu versions, then verify the container starts successfully without the setcap error while preserving the intended startup behavior.

Written by the indexing model from the issue text.