Skip to content

Add option to specify level-1 dir destination#1

Open
adybbroe wants to merge 1 commit into
nordsat:mainfrom
adybbroe:custom-level1-dir
Open

Add option to specify level-1 dir destination#1
adybbroe wants to merge 1 commit into
nordsat:mainfrom
adybbroe:custom-level1-dir

Conversation

@adybbroe

@adybbroe adybbroe commented Feb 18, 2024

Copy link
Copy Markdown

This PR adds an option to specify the name of the level-1directory path.

Signed-off-by: Adam.Dybbroe <a000680@c22526.ad.smhi.se>
@adybbroe

Copy link
Copy Markdown
Author

I failed to get the mounting to work properly when invoking podman run so I am linking a "volume" instead like this:
podman run --rm -v /san1/polar_in/direct_readout/aws:/data/aws:Z r-harbor.smhi.se/satsa/aws-processors

This means /data/aws in the container should correspond to how data are structured in the host under /san1/polar_in/direct_readout/awsand thus I would like to have contrl over the naming of the level-1 dir. Hence this PR.

@pnuu

pnuu commented Sep 25, 2024

Copy link
Copy Markdown
Contributor

You can mount the correct directory directly with -v just by giving the full path keeping the code simpler. I noticed that SELinux doesn't allow bind mounts and added similar mount commands to the READMEs of my two PRs.

@pnuu

pnuu commented Sep 25, 2024

Copy link
Copy Markdown
Contributor

Like this:

    podman run \
    -v /tmp/raw:/data/raw:Z \
    -v /tmp/L1:/data/L1:Z \
    --rm \
    localhost/aws_pre_proc

@pnuu

pnuu commented Jan 14, 2025

Copy link
Copy Markdown
Contributor

And to clarify, in your case you can do, assuming the raw and L1 are the directories on your host:

podman run --rm \
    -v /san1/polar_in/direct_readout/aws/raw:/data/raw:Z \
    -v /san1/polar_in/direct_readout/aws/L1:/data/L1:Z \
    r-harbor.smhi.se/satsa/aws-processors

This way we don't need to make the code unnecessarily more complicated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants