[Met_help] [rt.rap.ucar.edu #90213] History for Modification of MET container for HPC (UNCLASSIFIED)

[John Halley Gotway via RT]

----------------------------------------------------------------
  Initial Request
----------------------------------------------------------------

CLASSIFICATION: UNCLASSIFIED

I just learned that one of the ARL HPCs cannot run the MET Singularity
container due to an old kernel. This HPC is the one we use operationally for
running MET V5.2. The system administrators say the reason for the problem
is that root directory of the destination of bind-mounted paths must already
exist within the container. In this case, it is complaining because the home
directory gets bind-mounted into the container automatically
(/p/home/<your_username>). Modifying the container to include /p will fix
the problem. Is this something you could easily do?

Thanks.

R/
John

Mr. John W. Raby
U.S. Army Research Laboratory
White Sands Missile Range, NM 88002
(575) 678-2004 DSN 258-2004
FAX (575) 678-1230 DSN 258-1230
Email: john.w.raby2.civ at mail.mil


CLASSIFICATION: UNCLASSIFIED


----------------------------------------------------------------
  Complete Ticket History
----------------------------------------------------------------

Subject: Modification of MET container for HPC (UNCLASSIFIED)
From: John Halley Gotway
Time: Wed May 15 08:59:32 2019

Hi John,

I see you have a question about modifying the MET containers for use
on
your HPC.  If you're up for it, I'd encourage you to try to fix this
yourself.  Because I suspect you may run into other wrinkles like this
that
need to be fixed.  Once it's done and working for you, we can review
the
changes to the Dockerfile and add them into our build.

I assume you have a machine on which you can run Docker commands.  If
so,
here's what you'd do:

# Clone the git repo
git clone https://github.com/NCAR/container-dtc-met

# Build the Docker image
cd container-dtc-met/MET
docker build -t met-8.1 .

# Once you've successfully built the container the first time, try
editing
the "Dockerfile" in whatever way you need, and rebuilding...
docker build -t met-8.1_ARL .

Make sense?

For singularity, I believe it's easiest if the image lives on
DockerHub.
So you could push your resulting image up there... or I can help with
that
step.

Thanks,
John

On Wed, May 15, 2019 at 7:31 AM Raby, John W USA CIV via RT <
met_help at ucar.edu> wrote:

>
> Wed May 15 07:30:46 2019: Request 90213 was acted upon.
> Transaction: Ticket created by john.w.raby2.civ at mail.mil
>        Queue: met_help
>      Subject: Modification of MET container for HPC (UNCLASSIFIED)
>        Owner: Nobody
>   Requestors: john.w.raby2.civ at mail.mil
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90213 >
>
>
> CLASSIFICATION: UNCLASSIFIED
>
> I just learned that one of the ARL HPCs cannot run the MET
Singularity
> container due to an old kernel. This HPC is the one we use
operationally
> for
> running MET V5.2. The system administrators say the reason for the
problem
> is that root directory of the destination of bind-mounted paths must
> already
> exist within the container. In this case, it is complaining because
the
> home
> directory gets bind-mounted into the container automatically
> (/p/home/<your_username>). Modifying the container to include /p
will fix
> the problem. Is this something you could easily do?
>
> Thanks.
>
> R/
> John
>
> Mr. John W. Raby
> U.S. Army Research Laboratory
> White Sands Missile Range, NM 88002
> (575) 678-2004 DSN 258-2004
> FAX (575) 678-1230 DSN 258-1230
> Email: john.w.raby2.civ at mail.mil
>
>
> CLASSIFICATION: UNCLASSIFIED
>
>

------------------------------------------------
Subject: Modification of MET container for HPC (UNCLASSIFIED)
From: Raby, John W USA CIV
Time: Thu May 16 07:19:46 2019

CLASSIFICATION: UNCLASSIFIED

John -

Thanks for the detailed instructions on how to do the fix.
Unfortunately
neither my colleague in Maryland nor I have a machine right now which
can run
Docker commands. Our HPC system admin person is looking into what can
be done
with the Singularity container from their end and I'll let you know
what they
come up with.

R/
John

-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Wednesday, May 15, 2019 9:00 AM
To: Raby, John W CIV USARMY CCDC ARL (USA) <john.w.raby2.civ at mail.mil>
Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #90213] Modification of
MET
container for HPC (UNCLASSIFIED)

All active links contained in this email were disabled.  Please verify
the
identity of the sender, and confirm the authenticity of all links
contained
within the message prior to copying and pasting the address to a Web
browser.




----

Hi John,

I see you have a question about modifying the MET containers for use
on your
HPC.  If you're up for it, I'd encourage you to try to fix this
yourself.
Because I suspect you may run into other wrinkles like this that need
to be
fixed.  Once it's done and working for you, we can review the changes
to the
Dockerfile and add them into our build.

I assume you have a machine on which you can run Docker commands.  If
so,
here's what you'd do:

# Clone the git repo
git clone Caution-https://github.com/NCAR/container-dtc-met

# Build the Docker image
cd container-dtc-met/MET
docker build -t met-8.1 .

# Once you've successfully built the container the first time, try
editing the
"Dockerfile" in whatever way you need, and rebuilding...
docker build -t met-8.1_ARL .

Make sense?

For singularity, I believe it's easiest if the image lives on
DockerHub.
So you could push your resulting image up there... or I can help with
that
step.

Thanks,
John

On Wed, May 15, 2019 at 7:31 AM Raby, John W USA CIV via RT <
met_help at ucar.edu> wrote:

>
> Wed May 15 07:30:46 2019: Request 90213 was acted upon.
> Transaction: Ticket created by john.w.raby2.civ at mail.mil
>        Queue: met_help
>      Subject: Modification of MET container for HPC (UNCLASSIFIED)
>        Owner: Nobody
>   Requestors: john.w.raby2.civ at mail.mil
>       Status: new
>  Ticket <Caution-url:
> Caution-https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90213 >
>
>
> CLASSIFICATION: UNCLASSIFIED
>
> I just learned that one of the ARL HPCs cannot run the MET
Singularity
> container due to an old kernel. This HPC is the one we use
> operationally for running MET V5.2. The system administrators say
the
> reason for the problem is that root directory of the destination of
> bind-mounted paths must already exist within the container. In this
> case, it is complaining because the home directory gets bind-mounted
> into the container automatically (/p/home/<your_username>).
Modifying
> the container to include /p will fix the problem. Is this something
> you could easily do?
>
> Thanks.
>
> R/
> John
>
> Mr. John W. Raby
> U.S. Army Research Laboratory
> White Sands Missile Range, NM 88002
> (575) 678-2004 DSN 258-2004
> FAX (575) 678-1230 DSN 258-1230
> Email: john.w.raby2.civ at mail.mil
>
>
> CLASSIFICATION: UNCLASSIFIED
>
>

CLASSIFICATION: UNCLASSIFIED

------------------------------------------------