qnap-dev/container-apps

container-apps

An image and application list for QNAP Container Station.

Using your own image list

1. Click the “Fork” button in the upper-right corner of the GitHub interface.
2. Add your image and application information.
3. Change your preference application repository settings in Container Station.

Contributing

Want to help add more useful images and applications? Check out our contributing documentation.

These instructions may not be complete, please inform us if we should update anything. Better yet, submit a PR and improve them yourself.

Reporting Issues

Before opening any issue, please search for existing issues and read the Issue Guidelines, written by Nicolas Gallagher. After that if you find a bug or want to make feature request related to container-apps, please open a new issue.

Please report Container Station issues in QNAP Helpdesk.

Related Projects

• Docker Engine: Container Station using v17.09.1
• Docker Compose: Container Station using v1.22

License

Container-apps is licensed under the Apache License, Version 2.0. See LICENSE. for full license text.

container-apps's Issues

update gitlab within the container

How to update an old Gitlab 8.1.3 on the latest version without losing data?

TS-453 Pro

How to upgrade existing container app

I have managed to create a config that works with Container Station. But I cannot figure out how to update existing, already installed application to a new version when new containers are published on Docker Hub? Uninstalling the app and installing it again from provided configuration causes lost of all data because volumes mapped from containers are being removed during the uninstall process, too.

Improve qpkgcenter_eng.xml

YAML is more readable and smaller than XML. Besides, items with category application, such as GitLab, Redmine and Registry, are required to be indexed in qpkgcenter_eng.xml. I think such information should move into template//info.yml

Logo proposal for app

Hello, I'm designer😊. I want to know if you agree than I contribute to your project.
I think than you idea is amazing and will looks great with a face. 😎

Copy files to NAS

Hi All,

I would like to suggest an app for copy files to NAS.

Use Case

• User provide files list
• Copy to NAS by this app

Pull Image from Private Registry directory limitations

The Images can be within folders. In my case two levels in and because of the Image Name Field Validation rules, it does not allow "/". As a result, I get errors when I try to pull images from a private repository.

As an example, I have my private repository (other than docker) setup and tested properly.
registry.example.com/folder1/subfolder2/image:latest
However, it errors out. I've tried
foder1/subfoler2/image:latest
but this also fails.

Finally, I tried to export the docker image from my computer to import to the ContainerStation apps but the tar file contents are different.

1. Can you allow email verification for the registry username validation?
2. Can you allow "/" as part of the image pull from registry validation image input?
3. Can you give some examples of matching the containerstation export/import with the docker export/import features?

Docker issue not resolved: https://github.com/qnap-dev/container-apps/issues/53

This should have never been closed. To update a version in docker or to edit the docker yml is still not possible.

Update existing container to newer Docker Hub build (like issue #53)

Hi, I have managed to set up some Docker Containers with Container Station. But I cannot figure out how to update those existing, already installed applications to a new version from Docker Hub. As I am not an expert in Docker Containers, but some of the Containers are exposed to the WWW I need to keep them up to date without having to reconfigure the containers every time...

Feature Request: Workflow for updating image (or settings) used for a container

In Container Station, the web-based GUI does not provide a simple way to edit settings of any created container. While this works fine when images are kind of well understood and easy instructions exist to set them up, it does not work very well when one is experimenting/developing new images.

Some of the settings are changeable once the container is created. For example "CPU", "Memory" or "Auto-start" seem to be editable. It would be really useful if these edition capabilities were extended to the whole set of information concerning a container: the image used, the environment variables, the volumes that can be mounted, etc. A restart would then be required for changes to take effect.

This feature would allow one to experiment and adjust the use of containers through the web interface without the need to SSH into the machine, which will help on the usability of Container Station.

As of today, the only solution the user has (apart from SSH'ing into the machine as I saw in other threads) is to destroy and re-do the container from scratch, which is quite tedious.

build instruction does not work in docker-compose.yml

When trying to make my own LAMP template, i try to replace
image: php:7.1-apache
by

build: ./php
dockerfile: Dockerfile-php71

but i always have this error : Background task error for application: 'image'

the same docker-compose.yml works with command line (ssh on the NAS): docker-compose up

i've also tried with docker compose v2 without success :(

PS : is there a way to specify a dynamic name(via wizard?) in order to instanciate many times the same APP ? (docker-compose -p DYN_NAME up)

An explicit way to install/uninstall/upgrade App to host

Jessie Frazelle bring Docker Container to desktop. The problem on the solution is the command is too complex and long to correctly launch the container.

This proposal is aimed for simplifying "docker run" to a pure executable under $PATH such as /usr/bin.

To install Chrome container into host, for example, we may wrap following command provided by Jessie into a script named docker-chrome in the image jess/chrome

#!/bin/sh
docker run -it \
    --net host \ # may as well YOLO
    --cpuset 0 \ # control the cpu
    --memory 512mb \ # max memory it can use
    -v /tmp/.X11-unix:/tmp/.X11-unix \ # mount the X11 socket
    -e DISPLAY=unix$DISPLAY \ # pass the display
    -v $HOME/Downloads:/root/Downloads \ # optional, but nice
    -v $HOME/.config/google-chrome/:/data \ # if you want to save state
    --device /dev/snd \ # so we have sound
    --name chrome \
    jess/chrome

If I do docker run -v /a_tmp_path:/install jess/chrome install, this image will install the script to /a_tmp_path/usr/bin/docker-chrome. Then the system can check the file is safe or not. If everything is good, move to host's /usr/bin/

The system may also remember the files of application installed. When uninstalling the application, removing them all.

"Path is mounted but it is not shared" --> :shared propergationvalue causes issues

Hi all,

since an update of QNAP or volume change of the hdd I am facing a problem with the :shared setting of docker.

I used for my -v settings :shared to share the content within and between containers.

Now I am stuck with the problem that one docker container is not working anymore. It connects to my google drive and mounts it to the nas. So other containers can also work with it there is a :shared setting in the volume properties.

Everything worked until the update - but now I am only getting this error back:

Error response from daemon: linux mounts: Path /share/Media/cloud-encrypt is mounted on /share/CACHEDEV1_DATA but it is not a shared mount.

In QNAP /share is equal /share/CACHEDEV1_DATA. I don't understand why this is no shared mount, and settings like mount --make-shared also are not available on QNAP.

Without :shared the container itself is working - but not showing content from google drive.

Docker volume settings:

  -v /share/Multimedia/Media/local-media:/local-media:shared \ <- UNION
  -v /share/Multimedia/Media/local-decrypt:/local-decrypt:shared \ -> UNION
  -v /share/Multimedia/Media/cloud-decrypt:/cloud-decrypt:shared \ -> UNION
  -v /share/Multimedia/Media/cloud-encrypt:/cloud-encrypt:shared \

Do you have a idea how I could fix with inside of the shell?

Thanks for your help.

Client: Version: 17.07.0-ce API version: 1.31 Go version:
go1.8.3 Git commit: fd7dc00 Built: Thu Feb 8 15:57:38 2018 OS/Arch: linux/amd64

Server: Version: 17.07.0-ce API version: 1.31 (minimum version 1.12) Go version: go1.8.3 Git commit: fd7dc00 Built: Thu Feb 8 15:57:38 2018 OS/Arch: linux/amd64 Experimental: false 

It seems that it might be a docker bug regarding a default setting of MountFlags=slave when docker is started through systemd.

https://groups.google.com/forum/#!topic/portworx/A2vtTjjzSLI

Question is if you could help, since I also cannot find these config files of docker were I might unset MountFlags = shared

Thanks for your help.

Installation wizard

I would like to make my application TCP port configurable and let user decide its number in the wizard. Here is my docker-compose.yml file:

version: '2'
services:
  web:
    image: portainer/portainer:1.12.4
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    network_mode: host
    command:
      - --bind $PORTAINER_BIND

How should I implement it in the wizard/install.json file so the PORTAINER_BIND variable can be defined by a user during the installation process?

Wizards documentation

Hello,

I just got my new qnap NAS which I choose specifically because of support for containers, VMs and other similary cool things. In my work I'm used to install any service/app on our servers I want and so I have plenty ideas of what I would also like to see on my personal NAS at home.

Is there for example some complete documentation of wizards? Or maybe even some complete manual? I belive that there would be more applications available with some easily accessible documentation.

Thank you