You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tika.apache.org by "adjenks (Jira)" <ji...@apache.org> on 2022/10/28 20:57:00 UTC

[jira] [Created] (TIKA-3912) User in docker full build doesn't match user specified in latest source.

adjenks created TIKA-3912:
-----------------------------

             Summary: User in docker full build doesn't match user specified in latest source.
                 Key: TIKA-3912
                 URL: https://issues.apache.org/jira/browse/TIKA-3912
             Project: Tika
          Issue Type: Bug
          Components: tika-server
    Affects Versions: 2.5.0
            Reporter: adjenks


I recently used the "latest-full" docker image from docker hub.

More specifically:
apache/tika:latest-full
Digest:sha256:3a09399e89403e2503d5e018168f362295fdabe4b611c4d0eca2279a77bc7311
 
I noticed that in the source code that it specifies the user on line 67:
[https://github.com/apache/tika-docker/blob/6302d1daec3d59fabd60f79df198b04ee9cfc768/full/Dockerfile]

However, if you download the image, the user is root.

You can see this on image layer 14: [https://hub.docker.com/layers/apache/tika/latest-full/images/sha256-3a09399e89403e2503d5e018168f362295fdabe4b611c4d0eca2279a77bc7311?context=explore]

It doesn't specify root but it is blank instead of specifying the uid as was done previously.

So, the image previously specified a uid, and now it's back to root and it doesn't match the source. Why is this?



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