No, not immediately. After running the container for some minutes. I am aware of the link which is provided by you. But we don't have redis configure it on that particular server itself.
On Mon, Nov 2, 2020 at 6:48 PM Chesnay Schepler <ches...@apache.org> wrote: > I could not find any traces of *kdevtmpfsi* in our official docker image. > > The only references I could find on the web for *kdevtmpfsi* are that it > is some form of bitcoin malware, commonly associated with redis. > I do not believe that this was introduced by Flink, and would currently > conclude that either something in your environment is infected, or it was > introduced after the container was started. > Does it show up immediately after starting the container? > > There are several guides online for how to remove said process, here's one > <https://github.com/docker-library/redis/issues/217> for good measure. > > On 11/2/2020 1:42 PM, Avinash Tripathy wrote: > > No, I didn't modify anything into the docker file. Also we are not using > redis. > > On Mon, Nov 2, 2020 at 6:09 PM Chesnay Schepler <ches...@apache.org> > wrote: > >> What modifications have you made to the docker file? >> Are you using redis by any chance? >> >> On 11/2/2020 1:20 PM, Avinash Tripathy wrote: >> >> Hi, >> >> Based on the official image we have made the docker setup in our server. >> But after starting docker-compose.yml, there is one unknown process called >> "*kdevtmpfsi >> *" is taking more cpu. >> >> >> https://ci.apache.org/projects/flink/flink-docs-stable/ops/deployment/docker.html >> >> flink version: 1.11.2 >> >> Any idea about the above mentioned process. >> >> -- >> Thanks, >> Avinash >> >> >> > > -- > Thanks, > Avinash > > > -- Thanks, Avinash
