Re: [scl.org] ubi8/nodejs-16-minimal HOME env and PATH

2021-12-21 Thread Petr Kubat

Hi Jose,

thanks for the report! You are correct, the definitions should be in 
different ENV commands. I created a PR against sclorg repository:


https://github.com/sclorg/s2i-nodejs-container/pull/309

Petr

On 12/10/21 11:37 PM, Jose Gonzalez wrote:

Hi there!

I attempted to use the ubi8/nodejs-16-minimal image 
(https://catalog.redhat.com/software/containers/ubi8/nodejs-16-minimal/615aefd53f6014fa45ae1ae2 
) 
and couldn't seem to get the PATH to refer to the appropriate $HOME 
location. The result is that the node_modules paths are all relative 
to root ("/") instead of relative to the /opt/app-root/src path


$ docker run -it 
registry.access.redhat.com/ubi8/nodejs-16-minimal:latest 
 
printenv PATH

/node_modules/.bin/:/.npm-global/bin/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

In testing on my machine, it seems to be because the HOME variable and 
the PATH variable are declared in the same ENV action. Separating them 
resolved this for me, though it seems like it should have worked as 
expected.


Either way, I wanted to report it to see if there was something that I 
could do to resolve this, or if there was simply an error in how I was 
using this image.


Regards,

José R. González
Red Hat | Partner Lifecycle Engineering


___
SCLorg mailing list
SCLorg@redhat.com
https://listman.redhat.com/mailman/listinfo/sclorg
___
SCLorg mailing list
SCLorg@redhat.com
https://listman.redhat.com/mailman/listinfo/sclorg


Re: [scl.org] ubi8/nodejs14 update request

2021-05-12 Thread Petr Kubat

Hi Jim,

as was already said, the CVE fix already shipped (I guess your mail was 
stuck in some moderation queue?) and the image rebuilt to incorporate 
the fix.
So just for the record - the grade of the image only gets dropped when 
the CVE is actually fixed in the specific RHEL or RHSCL version and will 
drop lower the longer it takes to rebuild the image to add the CVE fix 
in. If there is a known vulnerability but the fix for it is not yet 
shipped, then the images will stay in grade A.


HTH,
Petr

On 2/8/21 10:08 PM, Jim Knochelmann wrote:

Hello,
I am interested in a version bump to image 
https://catalog.redhat.com/software/containers/ubi8/nodejs-14/5ed7887dd70cc50e69c2fabb 
 
.
There seems to be a discrepancy between the "security" tab, which is 
reporting a health index of "A" with no problems, and Red Hat's 
security info for nodejs 14 on RHEL 8: 
https://access.redhat.com/security/cve/CVE-2020-8277 
 which shows 
that CVE-2020-8277 has not yet been fixed.  Is CVE-2020-8277 a 
security concern?  It is possible that I am just interpreting the 
reports incorrectly.

If you are available on IBM slack, I am up at @JimKnochelmann .
Thank you,
Jim Knochelmann
Software Engineer
IBM Watson - Natural Language Understanding
+1 (720) 515-4454
jim.knochelm...@ibm.com


___
SCLorg mailing list
SCLorg@redhat.com
https://listman.redhat.com/mailman/listinfo/sclorg
___
SCLorg mailing list
SCLorg@redhat.com
https://listman.redhat.com/mailman/listinfo/sclorg


Re: [scl.org] rhscl/nodejs-8-rhel7 npm: command not found

2018-02-22 Thread Petr Kubat

Hi Adrian,

the npm command is actually installed inside the image, the collection 
is just not enabled in your case.


With `RUN bash -c "npm --version"` instead:

Sending build context to Docker daemon 478.7 kB
Step 1/3 : FROM registry.access.redhat.com/rhscl/nodejs-8-rhel7
Trying to pull repository 
registry.access.redhat.com/rhscl/nodejs-8-rhel7 ...
sha256:66ae3f2d4cd53e1fa232018079afe9ccb27f451d932b3a57d158609d0ecfbaa2: 
Pulling from registry.access.redhat.com/rhscl/nodejs-8-rhel7

9a32f102e677: Already exists
b8aa42cec17a: Already exists
84fbac7bf4f5: Pull complete
e347f5c3e6de: Pull complete
d7205639c454: Pull complete
Digest: 
sha256:66ae3f2d4cd53e1fa232018079afe9ccb27f451d932b3a57d158609d0ecfbaa2
Status: Downloaded newer image for 
registry.access.redhat.com/rhscl/nodejs-8-rhel7:latest

 ---> 505e241c8113
Step 2/3 : EXPOSE 8080
 ---> Running in 83a826e5a103
 ---> 9f3d2ed35228
Removing intermediate container 83a826e5a103
Step 3/3 : RUN bash -c "npm --version"
 ---> Running in b97f25fa5fba
5.3.0
 ---> 2c1e9751d2d5
Removing intermediate container b97f25fa5fba
Successfully built 2c1e9751d2d5

Hope this helps,
Petr


On 02/15/2018 11:32 AM, Höhn Adrian wrote:


Hi

I try to use your s2i image nodejs-8-rhel7 with the following 
Dockerfile config on OpenShift.


FROM registry.access.redhat.com/rhscl/nodejs-8-rhel7 


EXPOSE 8080

RUN npm --version

But when I try to build it on the Openshift platform I get the 
following error: *npm: command not found*


Can you explain me why npm cannot be found on this image and what I 
have to do to make it work? I expect that npm is part of a node image, 
not?


Thanks for your support,

Adrian

Openshift Logfile:

Pulling image registry.access.redhat.com/rhscl/nodejs-8-rhel7 ...

Pulled 2/5 layers, 41% complete

Pulled 3/5 layers, 63% complete

Pulled 4/5 layers, 84% complete

Pulled 5/5 layers, 100% complete

Extracting

Step 1 : FROM registry.access.redhat.com/rhscl/nodejs-8-rhel7

Trying to pull repository 
registry.access.redhat.com/rhscl/nodejs-8-rhel7 ...


sha256:66ae3f2d4cd53e1fa232018079afe9ccb27f451d932b3a57d158609d0ecfbaa2: 
Pulling from registry.access.redhat.com/rhscl/nodejs-8-rhel7


9a32f102e677: Already exists

b8aa42cec17a: Already exists

84fbac7bf4f5: Already exists

e347f5c3e6de: Already exists

d7205639c454: Already exists

Digest: 
sha256:66ae3f2d4cd53e1fa232018079afe9ccb27f451d932b3a57d158609d0ecfbaa2


Status: Image is up to date for 
registry.access.redhat.com/rhscl/nodejs-8-rhel7:latest


---> 505e241c8113

Step 2 : ENV ***

---> Running in 8bd5877d7e3b

---> 18f0b2af283a

Removing intermediate container 8bd5877d7e3b

Step 3 : EXPOSE 8080

---> Running in 6ec866f0d02c

---> 479b9e490fab

Removing intermediate container 6ec866f0d02c

Step 4 : RUN npm --version

---> Running in a00f61761e3a

/bin/sh: npm: command not found

error: build error: The command '/bin/sh -c npm --version' returned a 
non-zero code: 127




___
SCLorg mailing list
SCLorg@redhat.com
https://www.redhat.com/mailman/listinfo/sclorg


___
SCLorg mailing list
SCLorg@redhat.com
https://www.redhat.com/mailman/listinfo/sclorg