Added filebrowser #18
19
quadlets/filebrowser/filebrowser.container
Normal file
|
|
@ -0,0 +1,19 @@
|
|||
I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution. I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution.
I want to clarify what this is about and see if there's something we can do better about that. There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is I want to clarify what this is about and see if there's something we can do better about that.
There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is `calibre-web` because it wants a `metadata.db` from an existing `calibre` library. I added a `README.md` for that situation, but I seem to remember another one that needed to be bootstrapped.
These are holdovers from an outmoded method of handling docker user/group stuff inside containers. These are holdovers from an outmoded method of handling docker user/group stuff inside containers. `podman` should not require this anymore, and `1000` cannot be hardcoded. Even though upstreams and lsio containers use it as an example all the time, we have subuids and subgids, and `1000` is only correct if you are the only user on the system.
I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution. I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution.
|
||||
[Unit]
|
||||
|
I want to clarify what this is about and see if there's something we can do better about that. There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is I want to clarify what this is about and see if there's something we can do better about that.
There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is `calibre-web` because it wants a `metadata.db` from an existing `calibre` library. I added a `README.md` for that situation, but I seem to remember another one that needed to be bootstrapped.
These are holdovers from an outmoded method of handling docker user/group stuff inside containers. These are holdovers from an outmoded method of handling docker user/group stuff inside containers. `podman` should not require this anymore, and `1000` cannot be hardcoded. Even though upstreams and lsio containers use it as an example all the time, we have subuids and subgids, and `1000` is only correct if you are the only user on the system.
I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution. I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution.
|
||||
Description=Filebrowser Quadlet
|
||||
|
I want to clarify what this is about and see if there's something we can do better about that. There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is I want to clarify what this is about and see if there's something we can do better about that.
There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is `calibre-web` because it wants a `metadata.db` from an existing `calibre` library. I added a `README.md` for that situation, but I seem to remember another one that needed to be bootstrapped.
These are holdovers from an outmoded method of handling docker user/group stuff inside containers. These are holdovers from an outmoded method of handling docker user/group stuff inside containers. `podman` should not require this anymore, and `1000` cannot be hardcoded. Even though upstreams and lsio containers use it as an example all the time, we have subuids and subgids, and `1000` is only correct if you are the only user on the system.
I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution. I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution.
|
||||
|
||||
|
I want to clarify what this is about and see if there's something we can do better about that. There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is I want to clarify what this is about and see if there's something we can do better about that.
There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is `calibre-web` because it wants a `metadata.db` from an existing `calibre` library. I added a `README.md` for that situation, but I seem to remember another one that needed to be bootstrapped.
These are holdovers from an outmoded method of handling docker user/group stuff inside containers. These are holdovers from an outmoded method of handling docker user/group stuff inside containers. `podman` should not require this anymore, and `1000` cannot be hardcoded. Even though upstreams and lsio containers use it as an example all the time, we have subuids and subgids, and `1000` is only correct if you are the only user on the system.
I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution. I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution.
|
||||
[Service]
|
||||
|
I want to clarify what this is about and see if there's something we can do better about that. There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is I want to clarify what this is about and see if there's something we can do better about that.
There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is `calibre-web` because it wants a `metadata.db` from an existing `calibre` library. I added a `README.md` for that situation, but I seem to remember another one that needed to be bootstrapped.
These are holdovers from an outmoded method of handling docker user/group stuff inside containers. These are holdovers from an outmoded method of handling docker user/group stuff inside containers. `podman` should not require this anymore, and `1000` cannot be hardcoded. Even though upstreams and lsio containers use it as an example all the time, we have subuids and subgids, and `1000` is only correct if you are the only user on the system.
I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution. I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution.
|
||||
Restart=always
|
||||
|
I want to clarify what this is about and see if there's something we can do better about that. There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is I want to clarify what this is about and see if there's something we can do better about that.
There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is `calibre-web` because it wants a `metadata.db` from an existing `calibre` library. I added a `README.md` for that situation, but I seem to remember another one that needed to be bootstrapped.
These are holdovers from an outmoded method of handling docker user/group stuff inside containers. These are holdovers from an outmoded method of handling docker user/group stuff inside containers. `podman` should not require this anymore, and `1000` cannot be hardcoded. Even though upstreams and lsio containers use it as an example all the time, we have subuids and subgids, and `1000` is only correct if you are the only user on the system.
I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution. I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution.
|
||||
TimeoutStartSec=900
|
||||
|
I want to clarify what this is about and see if there's something we can do better about that. There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is I want to clarify what this is about and see if there's something we can do better about that.
There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is `calibre-web` because it wants a `metadata.db` from an existing `calibre` library. I added a `README.md` for that situation, but I seem to remember another one that needed to be bootstrapped.
These are holdovers from an outmoded method of handling docker user/group stuff inside containers. These are holdovers from an outmoded method of handling docker user/group stuff inside containers. `podman` should not require this anymore, and `1000` cannot be hardcoded. Even though upstreams and lsio containers use it as an example all the time, we have subuids and subgids, and `1000` is only correct if you are the only user on the system.
I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution. I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution.
|
||||
|
||||
|
I want to clarify what this is about and see if there's something we can do better about that. There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is I want to clarify what this is about and see if there's something we can do better about that.
There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is `calibre-web` because it wants a `metadata.db` from an existing `calibre` library. I added a `README.md` for that situation, but I seem to remember another one that needed to be bootstrapped.
These are holdovers from an outmoded method of handling docker user/group stuff inside containers. These are holdovers from an outmoded method of handling docker user/group stuff inside containers. `podman` should not require this anymore, and `1000` cannot be hardcoded. Even though upstreams and lsio containers use it as an example all the time, we have subuids and subgids, and `1000` is only correct if you are the only user on the system.
I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution. I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution.
|
||||
[Install]
|
||||
|
I want to clarify what this is about and see if there's something we can do better about that. There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is I want to clarify what this is about and see if there's something we can do better about that.
There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is `calibre-web` because it wants a `metadata.db` from an existing `calibre` library. I added a `README.md` for that situation, but I seem to remember another one that needed to be bootstrapped.
These are holdovers from an outmoded method of handling docker user/group stuff inside containers. These are holdovers from an outmoded method of handling docker user/group stuff inside containers. `podman` should not require this anymore, and `1000` cannot be hardcoded. Even though upstreams and lsio containers use it as an example all the time, we have subuids and subgids, and `1000` is only correct if you are the only user on the system.
I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution. I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution.
|
||||
WantedBy=multi-user.target default.target
|
||||
|
I want to clarify what this is about and see if there's something we can do better about that. There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is I want to clarify what this is about and see if there's something we can do better about that.
There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is `calibre-web` because it wants a `metadata.db` from an existing `calibre` library. I added a `README.md` for that situation, but I seem to remember another one that needed to be bootstrapped.
These are holdovers from an outmoded method of handling docker user/group stuff inside containers. These are holdovers from an outmoded method of handling docker user/group stuff inside containers. `podman` should not require this anymore, and `1000` cannot be hardcoded. Even though upstreams and lsio containers use it as an example all the time, we have subuids and subgids, and `1000` is only correct if you are the only user on the system.
I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution. I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution.
|
||||
|
||||
|
I want to clarify what this is about and see if there's something we can do better about that. There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is I want to clarify what this is about and see if there's something we can do better about that.
There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is `calibre-web` because it wants a `metadata.db` from an existing `calibre` library. I added a `README.md` for that situation, but I seem to remember another one that needed to be bootstrapped.
These are holdovers from an outmoded method of handling docker user/group stuff inside containers. These are holdovers from an outmoded method of handling docker user/group stuff inside containers. `podman` should not require this anymore, and `1000` cannot be hardcoded. Even though upstreams and lsio containers use it as an example all the time, we have subuids and subgids, and `1000` is only correct if you are the only user on the system.
I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution. I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution.
|
||||
[Container]
|
||||
|
I want to clarify what this is about and see if there's something we can do better about that. There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is I want to clarify what this is about and see if there's something we can do better about that.
There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is `calibre-web` because it wants a `metadata.db` from an existing `calibre` library. I added a `README.md` for that situation, but I seem to remember another one that needed to be bootstrapped.
These are holdovers from an outmoded method of handling docker user/group stuff inside containers. These are holdovers from an outmoded method of handling docker user/group stuff inside containers. `podman` should not require this anymore, and `1000` cannot be hardcoded. Even though upstreams and lsio containers use it as an example all the time, we have subuids and subgids, and `1000` is only correct if you are the only user on the system.
I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution. I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution.
|
||||
Image=docker.io/hurlenko/filebrowser:latest
|
||||
|
I want to clarify what this is about and see if there's something we can do better about that. There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is I want to clarify what this is about and see if there's something we can do better about that.
There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is `calibre-web` because it wants a `metadata.db` from an existing `calibre` library. I added a `README.md` for that situation, but I seem to remember another one that needed to be bootstrapped.
These are holdovers from an outmoded method of handling docker user/group stuff inside containers. These are holdovers from an outmoded method of handling docker user/group stuff inside containers. `podman` should not require this anymore, and `1000` cannot be hardcoded. Even though upstreams and lsio containers use it as an example all the time, we have subuids and subgids, and `1000` is only correct if you are the only user on the system.
I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution. I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution.
|
||||
ContainerName=filebrowser
|
||||
|
I want to clarify what this is about and see if there's something we can do better about that. There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is I want to clarify what this is about and see if there's something we can do better about that.
There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is `calibre-web` because it wants a `metadata.db` from an existing `calibre` library. I added a `README.md` for that situation, but I seem to remember another one that needed to be bootstrapped.
These are holdovers from an outmoded method of handling docker user/group stuff inside containers. These are holdovers from an outmoded method of handling docker user/group stuff inside containers. `podman` should not require this anymore, and `1000` cannot be hardcoded. Even though upstreams and lsio containers use it as an example all the time, we have subuids and subgids, and `1000` is only correct if you are the only user on the system.
I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution. I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution.
|
||||
|
||||
|
I want to clarify what this is about and see if there's something we can do better about that. There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is I want to clarify what this is about and see if there's something we can do better about that.
There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is `calibre-web` because it wants a `metadata.db` from an existing `calibre` library. I added a `README.md` for that situation, but I seem to remember another one that needed to be bootstrapped.
These are holdovers from an outmoded method of handling docker user/group stuff inside containers. These are holdovers from an outmoded method of handling docker user/group stuff inside containers. `podman` should not require this anymore, and `1000` cannot be hardcoded. Even though upstreams and lsio containers use it as an example all the time, we have subuids and subgids, and `1000` is only correct if you are the only user on the system.
I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution. I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution.
|
||||
Volume=/path/to/what/you/want/to/share:/data:z
|
||||
|
I want to clarify what this is about and see if there's something we can do better about that. There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is I want to clarify what this is about and see if there's something we can do better about that.
There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is `calibre-web` because it wants a `metadata.db` from an existing `calibre` library. I added a `README.md` for that situation, but I seem to remember another one that needed to be bootstrapped.
These are holdovers from an outmoded method of handling docker user/group stuff inside containers. These are holdovers from an outmoded method of handling docker user/group stuff inside containers. `podman` should not require this anymore, and `1000` cannot be hardcoded. Even though upstreams and lsio containers use it as an example all the time, we have subuids and subgids, and `1000` is only correct if you are the only user on the system.
I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution. I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution.
|
||||
Volume=fb-config:/config:z
|
||||
|
I want to clarify what this is about and see if there's something we can do better about that. There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is I want to clarify what this is about and see if there's something we can do better about that.
There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is `calibre-web` because it wants a `metadata.db` from an existing `calibre` library. I added a `README.md` for that situation, but I seem to remember another one that needed to be bootstrapped.
These are holdovers from an outmoded method of handling docker user/group stuff inside containers. These are holdovers from an outmoded method of handling docker user/group stuff inside containers. `podman` should not require this anymore, and `1000` cannot be hardcoded. Even though upstreams and lsio containers use it as an example all the time, we have subuids and subgids, and `1000` is only correct if you are the only user on the system.
I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution. I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution.
|
||||
Volume=fb-branding:/branding:z
|
||||
|
I want to clarify what this is about and see if there's something we can do better about that. There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is I want to clarify what this is about and see if there's something we can do better about that.
There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is `calibre-web` because it wants a `metadata.db` from an existing `calibre` library. I added a `README.md` for that situation, but I seem to remember another one that needed to be bootstrapped.
These are holdovers from an outmoded method of handling docker user/group stuff inside containers. These are holdovers from an outmoded method of handling docker user/group stuff inside containers. `podman` should not require this anymore, and `1000` cannot be hardcoded. Even though upstreams and lsio containers use it as an example all the time, we have subuids and subgids, and `1000` is only correct if you are the only user on the system.
I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution. I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution.
|
||||
|
||||
|
I want to clarify what this is about and see if there's something we can do better about that. There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is I want to clarify what this is about and see if there's something we can do better about that.
There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is `calibre-web` because it wants a `metadata.db` from an existing `calibre` library. I added a `README.md` for that situation, but I seem to remember another one that needed to be bootstrapped.
These are holdovers from an outmoded method of handling docker user/group stuff inside containers. These are holdovers from an outmoded method of handling docker user/group stuff inside containers. `podman` should not require this anymore, and `1000` cannot be hardcoded. Even though upstreams and lsio containers use it as an example all the time, we have subuids and subgids, and `1000` is only correct if you are the only user on the system.
I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution. I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution.
|
||||
PublishPort=8008:8080
|
||||
|
I want to clarify what this is about and see if there's something we can do better about that. There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is I want to clarify what this is about and see if there's something we can do better about that.
There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is `calibre-web` because it wants a `metadata.db` from an existing `calibre` library. I added a `README.md` for that situation, but I seem to remember another one that needed to be bootstrapped.
These are holdovers from an outmoded method of handling docker user/group stuff inside containers. These are holdovers from an outmoded method of handling docker user/group stuff inside containers. `podman` should not require this anymore, and `1000` cannot be hardcoded. Even though upstreams and lsio containers use it as an example all the time, we have subuids and subgids, and `1000` is only correct if you are the only user on the system.
I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution. I did try and add a post exec with a symlink but that failed I can look into this again though and try work out a solution.
|
||||
3
quadlets/filebrowser/filebrowser.volume
Normal file
|
|
@ -0,0 +1,3 @@
|
|||
[Volume]
|
||||
VolumeName=fb-config
|
||||
VolumeName=fb-branding
|
||||
I want to clarify what this is about and see if there's something we can do better about that.
There's another quadlet here that had a quirk similar to this. I need to check on which that was and revisit it also. One that stands out is
calibre-webbecause it wants ametadata.dbfrom an existingcalibrelibrary. I added aREADME.mdfor that situation, but I seem to remember another one that needed to be bootstrapped.These are holdovers from an outmoded method of handling docker user/group stuff inside containers.
podmanshould not require this anymore, and1000cannot be hardcoded. Even though upstreams and lsio containers use it as an example all the time, we have subuids and subgids, and1000is only correct if you are the only user on the system.