Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unpackerr #343

Open
kanecko opened this issue Mar 13, 2023 · 4 comments
Open

Unpackerr #343

kanecko opened this issue Mar 13, 2023 · 4 comments
Labels
New Rockon New Rockon Proposed

Comments

@kanecko
Copy link
Contributor

kanecko commented Mar 13, 2023

Hello all,

I will be adding the Unpackerr to the repo at some point :)
It will be based on the official multi-arch docker image https://hub.docker.com/r/golift/unpackerr

As far as I know, "--host" will not be needed.

@kanecko
Copy link
Contributor Author

kanecko commented Apr 14, 2023

Problem # 1: edit:solved
Unpackerr needs to use an existing share (e.g. from Transmission), because it watches for archives.

This means, when installing the Unpackerr RockOn, the user should NOT create a separate share. Instead, the user should use an existing share, which will be almost always used by another RockOn at the same time.

Long question short... what does the following mean, and what are our options here?
"If a Config or Data Share is assigned to more than one Rock-on, it could cause strange behavior."

Problem # 2: edit: a proposal
All of the following env vars are optional...
image

@phillxnet
Copy link
Member

@kanecko Hello there.
Re:

"If a Config or Data Share is assigned to more than one Rock-on, it could cause strange behavior."

This is to guide folks into having a seperation of concerns. I.e. having dedicated shares means no form one Rock-on can accidentally contaminate another. But there are for sure instances where one may want to access say the output of one Rock-on via the input/output of another. This should be doable but the warning is to help folks avoid things like two Rock-ons using say a configuration share and they end up re-configuring each other by way of competing/overlapping configuration files. That's it basically.

There is also now, in our testing channel and Stable RC releases , the following front-end filter:
rockstor/rockstor-core#2481

Hope that helps.
@Hooverdan96 and @FroggyFlox are more up on these matters than myself so if they comment further here then I'd go with what they say :) .

@kanecko
Copy link
Contributor Author

kanecko commented Apr 16, 2023

Am putting this on hold until #2094 #2280 #2012 are implemented.
Thus, I am implementing them next.

@Hooverdan96 Hooverdan96 added the New Rockon New Rockon Proposed label Dec 19, 2023
@phillxnet
Copy link
Member

Clarification, with links, on rockstor-core dependencies (previously indicated).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
New Rockon New Rockon Proposed
Projects
None yet
Development

No branches or pull requests

3 participants