Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/jim60105/docker-fc2-live-dl

This is the docker image for HoloArchivists/fc2-live-dl: Tool to download FC2 live streams. (Dockerfile, CI image build and test)
https://github.com/jim60105/docker-fc2-live-dl

docker docker-image dockerfile fc2 fc2live recording

Last synced: 13 days ago
JSON representation

This is the docker image for HoloArchivists/fc2-live-dl: Tool to download FC2 live streams. (Dockerfile, CI image build and test)

Awesome Lists containing this project

README 

        
# docker-fc2-live-dl



[![CodeFactor](https://www.codefactor.io/repository/github/jim60105/docker-fc2-live-dl/badge)](https://www.codefactor.io/repository/github/jim60105/docker-fc2-live-dl) [![GitHub Workflow Status (with event)](https://img.shields.io/github/actions/workflow/status/jim60105/docker-fc2-live-dl/scan.yml?label=IMAGE%20SCAN)](https://github.com/jim60105/docker-fc2-live-dl/actions/workflows/scan.yml)



This is the docker image for [HoloArchivists/fc2-live-dl: Tool to download FC2 live streams](https://github.com/HoloArchivists/fc2-live-dl) from the community.



Get the Dockerfile at [GitHub](https://github.com/jim60105/docker-fc2-live-dl), or pull the image from [ghcr.io](https://ghcr.io/jim60105/fc2-live-dl) or [quay.io](https://quay.io/repository/jim60105/fc2-live-dl?tab=tags).



## Usage Command



Mount the current directory as `/recordings` and run fc2-live-dl with additional input arguments.  

The downloaded files will be saved to where you run the command.



```bash

docker run -it -v ".:/recordings" ghcr.io/jim60105/fc2-live-dl [options] [fc2 url]

```



The `[options]`, `[fc2 url]` placeholder should be replaced with the options and arguments for fc2-live-dl. Check the [fc2-live-dl README](https://github.com/HoloArchivists/fc2-live-dl?tab=readme-ov-file#usage) for more information.



You can find all available tags at [ghcr.io](https://github.com/jim60105/docker-fc2-live-dl/pkgs/container/fc2-live-dl/versions?filters%5Bversion_type%5D=tagged) or [quay.io](https://quay.io/repository/jim60105/fc2-live-dl?tab=tags).



## Usage Command for autofc2



When using autofc2, it is recommended to use the provided [docker-compose.yml](docker-compose.yml) file.



Put the [autofc2.json](autofc2.json) file in the same directory as the [docker-compose.yml](docker-compose.yml) file, and execute the following command:



```bash

docker-compose up -d

```



Please check the [HoloArchivists/fc2-live-dl README](https://github.com/HoloArchivists/fc2-live-dl/tree/main?tab=readme-ov-file#autofc2) for more information about the json file.



> [!NOTE]  

> Please be aware that with our docker image, you need to **omit the `--config` parameter** and **use a relative path in outtmpl**.



## Available tags



This repository contains three Dockerfiles for building Docker images based on different base images:



| Dockerfile                                     | Base Image                                                                                                                         |

|------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|

| [Dockerfile](Dockerfile)                       | [Python official image 3-alpine](https://hub.docker.com/_/python/)                                                                 |

| [ubi.Dockerfile](ubi.Dockerfile)               | [Red Hat Universal Base Image 9 Minimal](https://catalog.redhat.com/software/containers/ubi9/ubi-minimal/615bd9b4075b022acc111bf5) |

| [distroless.Dockerfile](distroless.Dockerfile) | [distroless-python 3.12-debian12](https://github.com/alexdmoss/distroless-python)                                                  |



And, built with the following code version of fc2-live-dl: main branch, v2.2.0, v2.1.3.



| Code Version                                                                | Alpine                    | UBI          | Distroless          |

|-----------------------------------------------------------------------------|---------------------------|--------------|---------------------|

| [main branch](https://github.com/HoloArchivists/fc2-live-dl)                | `alpine`, `latest`        | `ubi`        | `distroless`        |

| [v2.2.0](https://github.com/HoloArchivists/fc2-live-dl/releases/tag/v2.2.0) | `v2.2.0`, `v2.2.0-alpine` | `v2.2.0-ubi` | `v2.2.0-distroless` |

| [v2.1.3](https://github.com/HoloArchivists/fc2-live-dl/releases/tag/v2.1.3) | `v2.1.3`, `v2.1.3-alpine` | `v2.1.3-ubi` | `v2.1.3-distroless` |



> [!TIP]

> I've notice that that both the UBI version and the Distroless version offer no advantages over the Alpine version. So _**please use the Alpine version**_ unless you have specific reasons not to. All of these base images are great, some of them were simply not that suitable for our project.



### Build Command



> [!IMPORTANT]  

> Clone the Git repository recursively to include submodules:  

> `git clone --recursive https://github.com/jim60105/docker-fc2-live-dl.git`



```bash

docker build -f Dockerfile -t fc2-live-dl .

```



> [!NOTE]  

> If you are using an earlier version of the docker client, it is necessary to [enable the BuildKit mode](https://docs.docker.com/build/buildkit/#getting-started) when building the image. This is because I used the `COPY --link` feature which enhances the build performance and was introduced in Buildx v0.8.  

> With the Docker Engine 23.0 and Docker Desktop 4.19, Buildx has become the default build client. So you won't have to worry about this when using the latest version.



## LICENSE



> [!NOTE]  

> The main program, [HoloArchivists/fc2-live-dl](https://github.com/HoloArchivists/fc2-live-dl), is distributed under [MIT](https://github.com/HoloArchivists/fc2-live-dl/blob/main/LICENSE).  

> Please consult their repository for access to the source code and licenses.  

> The following is the license for the Dockerfiles and CI workflows in this repository.



open graph



[GNU GENERAL PUBLIC LICENSE Version 3](LICENSE)



This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.



This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.



You should have received a copy of the GNU General Public License along with this program. If not, see .



> [!CAUTION]

> A GPLv3 licensed Dockerfile means that you _**MUST**_ **distribute the source code with the same license**, if you

>

> - Re-distribute the image. (You can simply point to this GitHub repository if you doesn't made any code changes.)

> - Distribute a image that uses code from this repository.

> - Or **distribute a image based on this image**. (`FROM ghcr.io/jim60105/fc2-live-dl` in your Dockerfile)

>

> "Distribute" means to make the image available for other people to download, usually by pushing it to a public registry. If you are solely using it for your personal purposes, this has no impact on you.

>

> Please consult the [LICENSE](LICENSE) for more details.



## 💭



The main reason I chose not to contribute my work back to the original repository is because I wanted to use the GPL license.



I am a strong supporter of open source and have a great passion for the GPL license. However, it's important to recognize that the GPL license has more restrictions compared to the MIT license, and people have valid reasons for not choosing it. I completely respect their decision. As it's not advisable to have multiple licenses in the same repository, I will distribute my work separately.



Now, you may be wondering why you should choose my image instead of the original one.



I have specifically created these images for fun... oops, focusing on **size, security, following best practices and industry policies.**



To assess the difference, you can pull the images and comparing the size and use scanning tools like [Snyk](https://snyk.io/), [Trivy](https://github.com/aquasecurity/trivy), or [Docker Scout](https://www.docker.com/products/docker-scout/) to scan the images. While I don't claim that my image is the MOST secure, I am confident that it is MORE secure.



I have spent years playing with containers and developing techniques to build more robust ones. I don't mean to criticize those who create "Oh, it works" containers. Developing this skill takes time, and I just happen to enjoy these toys more than others. I hope you can see their value.