You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Tim Allison (Jira)" <ji...@apache.org> on 2022/10/31 13:43:00 UTC
[jira] [Comment Edited] (TIKA-3912) User in docker full build doesn't match user specified in latest source.
[ https://issues.apache.org/jira/browse/TIKA-3912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626591#comment-17626591 ]
Tim Allison edited comment on TIKA-3912 at 10/31/22 1:42 PM:
-------------------------------------------------------------
When I build 922e22bb locally (on Ubuntu), which should be the same as the last released tag (2.5.0), the USER is not passed through. When I echo it during the build, the string is empty, and when I run the container the user is root.
I completely agree that there's a step in https://hub.docker.com/layers/apache/tika/2.5.0/images/sha256-d680d1d7136f35de43294e7b80ac495da463f069b0f1d59be1ebac5f0543f075?context=explore that shows the user getting tagged correctly, and in the container the user is there.
was (Author: tallison@mitre.org):
When I build 922e22bb locally (on Ubuntu), which should be the same as the last released tag (2.5.0, the USER is not passed through. When I echo it during the build, the string is empty, and when I run the container the user is root.
I completely agree that there's a step in https://hub.docker.com/layers/apache/tika/2.5.0/images/sha256-d680d1d7136f35de43294e7b80ac495da463f069b0f1d59be1ebac5f0543f075?context=explore that shows the user getting tagged correctly, and in the container the user is there.
> 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
> Priority: Minor
>
> 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)