[fix] hadolint warnings to base and rstudio Dockerfiles

[jstourac]

These changes shouldn't have any functional impact.

(cherry picked from commit a674246)

This is backport of #179; tracked in https://issues.redhat.com/browse/RHOAIENG-7884

[jiridanek]

/lgtm

[jiridanek]

/retest

[jstourac]

/retest

[jiridanek]

/retest

Won't help,

: Build image jupyter-datascience-anaconda-python-3.8 from the repository expand_more

on 2023b never succeeds

[jstourac]

: Build image jupyter-datascience-anaconda-python-3.8 from the repository expand_more

on 2023b never succeeds

I must have overlooked the anaconda failure before then, now I see it.

[jiridanek]

/override ci/prow/images

anaconda image fails to build, known issue

[openshift-ci]

@jiridanek: jiridanek unauthorized: /override is restricted to Repo administrators, approvers in top level OWNERS file, and the following github teams:.

In response to this:

/override ci/prow/images

anaconda image fails to build, known issue

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[jstourac]

Just realized that we have an upstream -> downstream branch regular updates. So maybe this is irrelevant and I should just check that the appropriate changes are done in a relevant branch in upstream, right? I'm moving this to draft until it's clear.

[jstourac]

Just realized that we have an upstream -> downstream branch regular updates. So maybe this is irrelevant and I should just check that the appropriate changes are done in a relevant branch in upstream, right? I'm moving this to draft until it's clear.

Hehe, the files that are changed in this PR aren't upstream, so we can't rely on upstream->downstream sync in these cases. Undrafted, ready for refiew/merge.

[jiridanek]

/lgtm

[openshift-ci]

@jstourac: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/images	1d8c6ae	link	true	/test images

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[jstourac]

@harshad16 do you mind to give your review/opinion so we can merge this eventually?

[harshad16]

do you mind to give your review/opinion so we can merge this eventually?

Could you please share why this is being pointed to the 2023b release branch? (i might seem have forgotten 🙈 )
Till i remember, we are providing only build configs with on imagestream pointing to latest tag, so i m unable to recollect why we are targeting 2023b branch.

[jstourac]

Could you please share why this is being pointed to the 2023b release branch? (i might seem have forgotten 🙈 ) Till i remember, we are providing only build configs with on imagestream pointing to latest tag, so i m unable to recollect why we are targeting 2023b branch.

Reason of this is the idea of backporting some CI checks to the 2023b branch as created in #330. Before the merge of that PR, I thought to have this merged separately first so that it is a reasonable small change and visible enough.

Another approach would be to put these hadolint warnings into the ignore and ditch this PR completely now.

[jiridanek]

The Jira (and comment https://issues.redhat.com/browse/RHOAIENG-7884?focusedId=24934565&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-24934565 in it) is about putting the CI check (and necessary fixes to make the check pass) into all relevant branches. I'd put this in.

[harshad16]

Thank you for the response, lgtm.
/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: harshad16

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [harshad16]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment