adding firefox image to the subuser

I followed all the steps to create subuser given on

I am not able to create firefox image and not able to restrict the access to the Downloads folder as given in the video and documentation

  • docker-compose: no gunicorn when trying “up” container
  • RabbitMQ doesn't respects Docker memory limits
  • Bluemix Docker container cf ic run doesn't seem to accept -p sub-command
  • How to pass docker arguments during docker run command or docker-compose up command
  • Pros and cons of multi-threading vs containers for a consumer program [closed]
  • Flocker: How do I provide a custom /etc/mongodb.conf file?
  • Please provide me with the solution. i need it for my project

  • Docker couchbase cbbackup/cbtransfer/cbrestore tools
  • Debugging Elastic Beanstalk Docker run failures?
  • What is the difference between Docker Hub Registery and
  • Change swappiness for docker container
  • Like “make” for Docker
  • Cant access my Docker DotNet core website
  • One Solution collect form web for “adding firefox image to the subuser”

    You would create a folder my-subuser-images and then create a second folder firefox in the first one:


    In the firefox folder, you need to create yet another sub-folder: docker-image

    Once you have done that you need to create two files:




    Your file layout should look like the one found at the subuser-default-repository

    In the permissions.json file, you tell subuser what Firefox is allowed to do:

    {"description":"A popular web browser."

    Here is an overview of the permissions that I just set:

    "gui": Allows Firefox to display windows to X11 securely using the XPRA X11 bridge
    "sound-card": Allows Firefox to communicate with your sound card
    "allow-network-access": Allows Firefox to access the network
    "basic-common-permissions": Allows Firefox to do some basic things like save settings to it's own specially contained home directory, see the LOCAL and timezone ect.

    It does NOT however, allow Firefox to access any files outside of it’s own subuser. You could add a user-dirs permission to allow it to access the Downloads directory, for example, if you wished.

    Once you have created a permissions.json file, you can go on to create a SubuserImagefile.

    The docker-image/SubuserImagefile should look just like a Dockerfile:

    FROM ubuntu
    RUN apt-get update && apt-get upgrade -y && apt-get install -yq firefox

    Now you are done setting up your subuser image.

    You can create a firefox subuser by running:

    $ subuser subuser add firefox firefox@/home/student/my-subuser-images

    You can run the firefox subuser by running:

    $ subuser run firefox

    You can create more than one firefox subuser. This is useful, if you want to have more than one Facebook account or Google account and not have to log out/in all the time. It is also usefull if you want to reduce the risk of cross-site scripting when you do internet banking.

    subuser subuser add internet-banking firefox@/home/student/my-subuser-images

    You can run your internet-banking subuser with the command

    subuser run internet-banking

    You can access a subuser’s home directory by visiting ~/.subuser/homes.

    You can share your subuser images with others, to reduce the burden of sandboxing applications for everybody. If you want to share your Firefox image, you can cd to my-subuser-images and turn that folder into a git repository:

    $ cd ~/my-subuser-images
    $ git init
    $ git add .
    $ git commit -m "Add Firefox image"

    If you then push this git repo somewhere, then others can install your Firefox image easilly with the command:

    $ subuser subuser add firefox firefox@

    They would run that subuser in the same way as if they had done the setup locally.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.