[{"_1":2,"_180":-5,"_181":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_155":156},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11,"_20":17},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_23":24,"_25":-5,"_26":11,"_27":11,"_28":29,"_30":31,"_32":-5,"_33":11,"_34":35,"_84":-5,"_85":86,"_146":-5,"_147":11,"_148":17,"_149":11,"_150":-5,"_151":11,"_152":-5,"_153":154},"canonicalUrl","https://hub.docker.com/r/olivercullimore/docker-firefox/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","olivercullimore","reponame","docker-firefox","cloudBuildSource","isAutobuildsAvailable","repo",{"_36":37,"_38":39,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":51,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":70,"_75":11,"_76":77,"_81":29,"_82":83},"categories",[],"content_types",[40],"image","date_registered","2021-09-05T20:29:43.471239Z","description","","is_private","last_updated","2021-09-06T07:48:41.317777Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[52],"application/vnd.docker.distribution.manifest.list.v2+json","name","pull_count",227,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","# Docker container for Firefox\n[![Docker Image Size](https://img.shields.io/docker/image-size/jlesage/firefox/latest)](https://hub.docker.com/r/jlesage/firefox/tags) [![Build Status](https://drone.le-sage.com/api/badges/jlesage/docker-firefox/status.svg)](https://drone.le-sage.com/jlesage/docker-firefox) [![GitHub Release](https://img.shields.io/github/release/jlesage/docker-firefox.svg)](https://github.com/jlesage/docker-firefox/releases/latest) [![Donate](https://img.shields.io/badge/Donate-PayPal-green.svg)](https://paypal.me/JocelynLeSage/0usd)\n\nThis is a Docker container for [Firefox](https://www.mozilla.org/en-US/firefox/).\n\nThe GUI of the application is accessed through a modern web browser (no installation or configuration needed on the client side) or via any VNC client.\n\n---\n\n[![Firefox logo](https://images.weserv.nl/?url=raw.githubusercontent.com/jlesage/docker-templates/master/jlesage/images/firefox-icon.png&w=200)](https://www.mozilla.org/en-US/firefox/)[![Firefox](https://dummyimage.com/400x110/ffffff/575757&text=Firefox)](https://www.mozilla.org/en-US/firefox/)\n\nMozilla Firefox is a free and open-source web browser developed by Mozilla Foundation and its subsidiary, Mozilla Corporation.\n\n---\n\n## Table of Content\n\n * [Docker container for Firefox](#docker-container-for-firefox)\n * [Table of Content](#table-of-content)\n * [Quick Start](#quick-start)\n * [Usage](#usage)\n * [Environment Variables](#environment-variables)\n * [Data Volumes](#data-volumes)\n * [Ports](#ports)\n * [Changing Parameters of a Running Container](#changing-parameters-of-a-running-container)\n * [Docker Compose File](#docker-compose-file)\n * [Docker Image Update](#docker-image-update)\n * [Synology](#synology)\n * [unRAID](#unraid)\n * [User/Group IDs](#usergroup-ids)\n * [Accessing the GUI](#accessing-the-gui)\n * [Security](#security)\n * [SSVNC](#ssvnc)\n * [Certificates](#certificates)\n * [VNC Password](#vnc-password)\n * [Reverse Proxy](#reverse-proxy)\n * [Routing Based on Hostname](#routing-based-on-hostname)\n * [Routing Based on URL Path](#routing-based-on-url-path)\n * [Shell Access](#shell-access)\n * [Increasing Shared Memory Size](#increasing-shared-memory-size)\n * [Allowing the membarrier System Call](#allowing-the-membarrier-system-call)\n * [Sound Support](#sound-support)\n * [Setting Firefox Preferences Via Environment Variables](#setting-firefox-preferences-via-environment-variables)\n * [Troubleshooting](#troubleshooting)\n * [Crashes](#crashes)\n * [Support or Contact](#support-or-contact)\n\n## Quick Start\n\n**NOTE**: The Docker command provided in this quick start is given as an example\nand parameters should be adjusted to your need.\n\nLaunch the Firefox docker container with the following command:\n```\ndocker run -d \\\n --name=firefox \\\n -p 5800:5800 \\\n -v /docker/appdata/firefox:/config:rw \\\n --shm-size 2g \\\n jlesage/firefox\n```\n\nWhere:\n - `/docker/appdata/firefox`: This is where the application stores its configuration, log and any files needing persistency.\n\nBrowse to `http://your-host-ip:5800` to access the Firefox GUI.\n\n## Usage\n\n```\ndocker run [-d] \\\n --name=firefox \\\n [-e =]... \\\n [-v :[:PERMISSIONS]]... \\\n [-p :]... \\\n --shm-size VALUE \\\n jlesage/firefox\n```\n| Parameter | Description |\n|-----------|-------------|\n| -d | Run the container in the background. If not set, the container runs in the foreground. |\n| -e | Pass an environment variable to the container. See the [Environment Variables](#environment-variables) section for more details. |\n| -v | Set a volume mapping (allows to share a folder/file between the host and the container). See the [Data Volumes](#data-volumes) section for more details. |\n| -p | Set a network port mapping (exposes an internal container port to the host). See the [Ports](#ports) section for more details. |\n| --shm-size | Set the size of `/dev/shm` to `VALUE`. The format of `VALUE` is ``, where `number` must be greater than `0` and `unit` can be `b` (bytes), `k` (kilobytes), `m` (megabytes), or `g` (gigabytes). **NOTE**: To avoid crashes, it is recommended to set this value to `2g`. |\n\n### Environment Variables\n\nTo customize some properties of the container, the following environment\nvariables can be passed via the `-e` parameter (one for each variable). Value\nof this parameter has the format `=`.\n\n| Variable | Description | Default |\n|----------------|----------------------------------------------|---------|\n|`USER_ID`| ID of the user the application runs as. See [User/Group IDs](#usergroup-ids) to better understand when this should be set. | `1000` |\n|`GROUP_ID`| ID of the group the application runs as. See [User/Group IDs](#usergroup-ids) to better understand when this should be set. | `1000` |\n|`SUP_GROUP_IDS`| Comma-separated list of supplementary group IDs of the application. | (unset) |\n|`UMASK`| Mask that controls how file permissions are set for newly created files. The value of the mask is in octal notation. By default, this variable is not set and the default umask of `022` is used, meaning that newly created files are readable by everyone, but only writable by the owner. See the following online umask calculator: http://wintelguy.com/umask-calc.pl | (unset) |\n|`TZ`| [TimeZone] of the container. Timezone can also be set by mapping `/etc/localtime` between the host and the container. | `Etc/UTC` |\n|`KEEP_APP_RUNNING`| When set to `1`, the application will be automatically restarted if it crashes or if a user quits it. | `0` |\n|`APP_NICENESS`| Priority at which the application should run. A niceness value of -20 is the highest priority and 19 is the lowest priority. By default, niceness is not set, meaning that the default niceness of 0 is used. **NOTE**: A negative niceness (priority increase) requires additional permissions. In this case, the container should be run with the docker option `--cap-add=SYS_NICE`. | (unset) |\n|`CLEAN_TMP_DIR`| When set to `1`, all files in the `/tmp` directory are deleted during the container startup. | `1` |\n|`DISPLAY_WIDTH`| Width (in pixels) of the application's window. | `1280` |\n|`DISPLAY_HEIGHT`| Height (in pixels) of the application's window. | `768` |\n|`SECURE_CONNECTION`| When set to `1`, an encrypted connection is used to access the application's GUI (either via a web browser or VNC client). See the [Security](#security) section for more details. | `0` |\n|`VNC_PASSWORD`| Password needed to connect to the application's GUI. See the [VNC Password](#vnc-password) section for more details. | (unset) |\n|`X11VNC_EXTRA_OPTS`| Extra options to pass to the x11vnc server running in the Docker container. **WARNING**: For advanced users. Do not use unless you know what you are doing. | (unset) |\n|`ENABLE_CJK_FONT`| When set to `1`, open-source computer font `WenQuanYi Zen Hei` is installed. This font contains a large range of Chinese/Japanese/Korean characters. | `0` |\n\n### Data Volumes\n\nThe following table describes data volumes used by the container. The mappings\nare set via the `-v` parameter. Each mapping is specified with the following\nformat: `:[:PERMISSIONS]`.\n\n| Container path | Permissions | Description |\n|-----------------|-------------|-------------|\n|`/config`| rw | This is where the application stores its configuration, log and any files needing persistency. |\n\n### Ports\n\nHere is the list of ports used by the container. They can be mapped to the host\nvia the `-p` parameter (one per port mapping). Each mapping is defined in the\nfollowing format: `:`. The port number inside the\ncontainer cannot be changed, but you are free to use any port on the host side.\n\n| Port | Mapping to host | Description |\n|------|-----------------|-------------|\n| 5800 | Mandatory | Port used to access the application's GUI via the web interface. |\n| 5900 | Optional | Port used to access the application's GUI via the VNC protocol. Optional if no VNC client is used. |\n\n### Changing Parameters of a Running Container\n\nAs can be seen, environment variables, volume and port mappings are all specified\nwhile creating the container.\n\nThe following steps describe the method used to add, remove or update\nparameter(s) of an existing container. The general idea is to destroy and\nre-create the container:\n\n 1. Stop the container (if it is running):\n```\ndocker stop firefox\n```\n 2. Remove the container:\n```\ndocker rm firefox\n```\n 3. Create/start the container using the `docker run` command, by adjusting\n parameters as needed.\n\n**NOTE**: Since all application's data is saved under the `/config` container\nfolder, destroying and re-creating a container is not a problem: nothing is lost\nand the application comes back with the same state (as long as the mapping of\nthe `/config` folder remains the same).\n\n## Docker Compose File\n\nHere is an example of a `docker-compose.yml` file that can be used with\n[Docker Compose](https://docs.docker.com/compose/overview/).\n\nMake sure to adjust according to your needs. Note that only mandatory network\nports are part of the example.\n\n```yaml\nversion: '3'\nservices:\n firefox:\n image: jlesage/firefox\n ports:\n - \"5800:5800\"\n volumes:\n - \"/docker/appdata/firefox:/config:rw\"\n```\n\n## Docker Image Update\n\nBecause features are added, issues are fixed, or simply because a new version\nof the containerized application is integrated, the Docker image is regularly\nupdated. Different methods can be used to update the Docker image.\n\nThe system used to run the container may have a built-in way to update\ncontainers. If so, this could be your primary way to update Docker images.\n\nAn other way is to have the image be automatically updated with [Watchtower].\nWatchtower is a container-based solution for automating Docker image updates.\nThis is a \"set and forget\" type of solution: once a new image is available,\nWatchtower will seamlessly perform the necessary steps to update the container.\n\nFinally, the Docker image can be manually updated with these steps:\n\n 1. Fetch the latest image:\n```\ndocker pull jlesage/firefox\n```\n 2. Stop the container:\n```\ndocker stop firefox\n```\n 3. Remove the container:\n```\ndocker rm firefox\n```\n 4. Create and start the container using the `docker run` command, with the\nthe same parameters that were used when it was deployed initially.\n\n[Watchtower]: https://github.com/containrrr/watchtower\n\n### Synology\n\nFor owners of a Synology NAS, the following steps can be used to update a\ncontainer image.\n\n 1. Open the *Docker* application.\n 2. Click on *Registry* in the left pane.\n 3. In the search bar, type the name of the container (`jlesage/firefox`).\n 4. Select the image, click *Download* and then choose the `latest` tag.\n 5. Wait for the download to complete. A notification will appear once done.\n 6. Click on *Container* in the left pane.\n 7. Select your Firefox container.\n 8. Stop it by clicking *Action*->*Stop*.\n 9. Clear the container by clicking *Action*->*Reset* (or *Action*->*Clear* if\n you don't have the latest *Docker* application). This removes the\n container while keeping its configuration.\n 10. Start the container again by clicking *Action*->*Start*. **NOTE**: The\n container may temporarily disappear from the list while it is re-created.\n\n### unRAID\n\nFor unRAID, a container image can be updated by following these steps:\n\n 1. Select the *Docker* tab.\n 2. Click the *Check for Updates* button at the bottom of the page.\n 3. Click the *update ready* link of the container to be updated.\n\n## User/Group IDs\n\nWhen using data volumes (`-v` flags), permissions issues can occur between the\nhost and the container. For example, the user within the container may not\nexist on the host. This could prevent the host from properly accessing files\nand folders on the shared volume.\n\nTo avoid any problem, you can specify the user the application should run as.\n\nThis is done by passing the user ID and group ID to the container via the\n`USER_ID` and `GROUP_ID` environment variables.\n\nTo find the right IDs to use, issue the following command on the host, with the\nuser owning the data volume on the host:\n\n id \n\nWhich gives an output like this one:\n```\nuid=1000(myuser) gid=1000(myuser) groups=1000(myuser),4(adm),24(cdrom),27(sudo),46(plugdev),113(lpadmin)\n```\n\nThe value of `uid` (user ID) and `gid` (group ID) are the ones that you should\nbe given the container.\n\n## Accessing the GUI\n\nAssuming that container's ports are mapped to the same host's ports, the\ngraphical interface of the application can be accessed via:\n\n * A web browser:\n```\nhttp://:5800\n```\n\n * Any VNC client:\n```\n:5900\n```\n\n## Security\n\nBy default, access to the application's GUI is done over an unencrypted\nconnection (HTTP or VNC).\n\nSecure connection can be enabled via the `SECURE_CONNECTION` environment\nvariable. See the [Environment Variables](#environment-variables) section for\nmore details on how to set an environment variable.\n\nWhen enabled, application's GUI is performed over an HTTPs connection when\naccessed with a browser. All HTTP accesses are automatically redirected to\nHTTPs.\n\nWhen using a VNC client, the VNC connection is performed over SSL. Note that\nfew VNC clients support this method. [SSVNC] is one of them.\n\n[SSVNC]: http://www.karlrunge.com/x11vnc/ssvnc.html\n\n### SSVNC\n\n[SSVNC] is a VNC viewer that adds encryption security to VNC connections.\n\nWhile the Linux version of [SSVNC] works well, the Windows version has some\nissues. At the time of writing, the latest version `1.0.30` is not functional,\nas a connection fails with the following error:\n```\nReadExact: Socket error while reading\n```\nHowever, for your convenience, an unofficial and working version is provided\nhere:\n\nhttps://github.com/jlesage/docker-baseimage-gui/raw/master/tools/ssvnc_windows_only-1.0.30-r1.zip\n\nThe only difference with the official package is that the bundled version of\n`stunnel` has been upgraded to version `5.49`, which fixes the connection\nproblems.\n\n### Certificates\n\nHere are the certificate files needed by the container. By default, when they\nare missing, self-signed certificates are generated and used. All files have\nPEM encoded, x509 certificates.\n\n| Container Path | Purpose | Content |\n|---------------------------------|----------------------------|---------|\n|`/config/certs/vnc-server.pem` |VNC connection encryption. |VNC server's private key and certificate, bundled with any root and intermediate certificates.|\n|`/config/certs/web-privkey.pem` |HTTPs connection encryption.|Web server's private key.|\n|`/config/certs/web-fullchain.pem`|HTTPs connection encryption.|Web server's certificate, bundled with any root and intermediate certificates.|\n\n**NOTE**: To prevent any certificate validity warnings/errors from the browser\nor VNC client, make sure to supply your own valid certificates.\n\n**NOTE**: Certificate files are monitored and relevant daemons are automatically\nrestarted when changes are detected.\n\n### VNC Password\n\nTo restrict access to your application, a password can be specified. This can\nbe done via two methods:\n * By using the `VNC_PASSWORD` environment variable.\n * By creating a `.vncpass_clear` file at the root of the `/config` volume.\n This file should contain the password in clear-text. During the container\n startup, content of the file is obfuscated and moved to `.vncpass`.\n\nThe level of security provided by the VNC password depends on two things:\n * The type of communication channel (encrypted/unencrypted).\n * How secure the access to the host is.\n\nWhen using a VNC password, it is highly desirable to enable the secure\nconnection to prevent sending the password in clear over an unencrypted channel.\n\n**ATTENTION**: Password is limited to 8 characters. This limitation comes from\nthe Remote Framebuffer Protocol [RFC](https://tools.ietf.org/html/rfc6143) (see\nsection [7.2.2](https://tools.ietf.org/html/rfc6143#section-7.2.2)). Any\ncharacters beyond the limit are ignored.\n\n## Reverse Proxy\n\nThe following sections contain NGINX configurations that need to be added in\norder to reverse proxy to this container.\n\nA reverse proxy server can route HTTP requests based on the hostname or the URL\npath.\n\n### Routing Based on Hostname\n\nIn this scenario, each hostname is routed to a different application/container.\n\nFor example, let's say the reverse proxy server is running on the same machine\nas this container. The server would proxy all HTTP requests sent to\n`firefox.domain.tld` to the container at `127.0.0.1:5800`.\n\nHere are the relevant configuration elements that would be added to the NGINX\nconfiguration:\n\n```\nmap $http_upgrade $connection_upgrade {\n\tdefault upgrade;\n\t'' close;\n}\n\nupstream docker-firefox {\n\t# If the reverse proxy server is not running on the same machine as the\n\t# Docker container, use the IP of the Docker host here.\n\t# Make sure to adjust the port according to how port 5800 of the\n\t# container has been mapped on the host.\n\tserver 127.0.0.1:5800;\n}\n\nserver {\n\t[...]\n\n\tserver_name firefox.domain.tld;\n\n\tlocation / {\n\t proxy_pass http://docker-firefox;\n\t}\n\n\tlocation /websockify {\n\t\tproxy_pass http://docker-firefox;\n\t\tproxy_http_version 1.1;\n\t\tproxy_set_header Upgrade $http_upgrade;\n\t\tproxy_set_header Connection $connection_upgrade;\n\t\tproxy_read_timeout 86400;\n\t}\n}\n\n```\n\n### Routing Based on URL Path\n\nIn this scenario, the hostname is the same, but different URL paths are used to\nroute to different applications/containers.\n\nFor example, let's say the reverse proxy server is running on the same machine\nas this container. The server would proxy all HTTP requests for\n`server.domain.tld/firefox` to the container at `127.0.0.1:5800`.\n\nHere are the relevant configuration elements that would be added to the NGINX\nconfiguration:\n\n```\nmap $http_upgrade $connection_upgrade {\n\tdefault upgrade;\n\t'' close;\n}\n\nupstream docker-firefox {\n\t# If the reverse proxy server is not running on the same machine as the\n\t# Docker container, use the IP of the Docker host here.\n\t# Make sure to adjust the port according to how port 5800 of the\n\t# container has been mapped on the host.\n\tserver 127.0.0.1:5800;\n}\n\nserver {\n\t[...]\n\n\tlocation = /firefox {return 301 $scheme://$http_host/firefox/;}\n\tlocation /firefox/ {\n\t\tproxy_pass http://docker-firefox/;\n\t\tlocation /firefox/websockify {\n\t\t\tproxy_pass http://docker-firefox/websockify/;\n\t\t\tproxy_http_version 1.1;\n\t\t\tproxy_set_header Upgrade $http_upgrade;\n\t\t\tproxy_set_header Connection $connection_upgrade;\n\t\t\tproxy_read_timeout 86400;\n\t\t}\n\t}\n}\n\n```\n## Shell Access\n\nTo get shell access to the running container, execute the following command:\n\n```\ndocker exec -ti CONTAINER sh\n```\n\nWhere `CONTAINER` is the ID or the name of the container used during its\ncreation (e.g. `crashplan-pro`).\n\n## Increasing Shared Memory Size\n\nTo prevent crashes from happening when running Firefox\ninside a Docker container, the size of the shared memory located at `/dev/shm`\nmust be increased. The issue is documented [here].\n\nBy default, the size is 64MB, which is not enough. It is recommended to use a\nsize of 2GB. This value is arbitrary, but known to work well. Setting the\nsize of `/dev/shm` can be done via two method:\n\n - By adding the `--shm-size 2g` parameter to the `docker run` command. See\n the [Usage](#usage) section for more details.\n - By using shared memory of the host, by mapping `/dev/shm` via the parameter\n `-v /dev/shm:/dev/shm` of the `docker run` command.\n\n## Allowing the membarrier System Call\n\nTo properly work, recent versions of Firefox need the\n`membarrier` system call. Without it, tabs would frequently crash.\n\nDocker uses [seccomp profile] to restrict system calls available to the\ncontainer. Before Docker version `20.10.0`, the `membarrier` system call was\nnot allowed in the default profile. If you run a such version, you can use one\nof the following solutions, from the most to the least secure, to provide the\ncontainer permission to use this sytem call:\n\n 1. Run the container with a custom seccomp profile allowing the `membarrier`\n system call. The [latest official seccomp profile] can be used. Download\n the file and then add the following parameter when creating the container:\n `--security-opt seccomp=/path/to/seccomp_profile.json`.\n 2. Run the container without the default seccomp profile (thus allowing all\n system calls). Use the following parameter when creating the container:\n `--security-opt seccomp=unconfined`.\n 3. Run the container in privileged mode. This effectively disables usage of\n seccomp. Add the `--privileged` parameter when creating the container.\n\n## Sound Support\n\nFor Firefox to be able to use the audio device available on\nthe host, `/dev/snd` must be exposed to the container by adding the\n`--device /dev/snd` parameter to the `docker run` command.\n\n## Setting Firefox Preferences Via Environment Variables\n\nFirefox preferences can be set via environment variables\npassed to the container. During the startup, a script process all these\nvariables and modify the preference file accordingly.\n\nThe name of the environment variable must start with `FF_PREF_`, followed by a\nstring of your choice. For example, `FF_PREF_MY_PREF` is a valid name.\n\nThe content of the variable should be in the format `NAME=VAL`, where `NAME` is\nthe name of the preference (as found in the `about:config` page) and `VAL` is\nits value. A value can be one of the following types:\n - string\n - integer\n - boolean\n\nIt is important to note that a value of type `string` should be surrounded by\ndouble quotes. Other types don't need them.\n\nFor example, to set the `network.proxy.http` preference, one would pass the\nenvironment variable to the container by adding the following argument to the\n`docker run` command:\n\n```\n-e \"FF_PREF_HTTP_PROXY=network.proxy.http=\\\"proxy.example.com\\\"\"\n```\n\nIf a preference needs to be *removed*, its value should be set to `UNSET`. For\nexample:\n\n```\n-e \"FF_PREF_HTTP_PROXY=network.proxy.http=UNSET\"\n```\n\n**NOTE**: This is an advanced usage and it is recommended to set preferences\nvia Firefox directly.\n\n## Troubleshooting\n\n### Crashes\n\nIf Firefox is crashing frequently, make sure that:\n - The size of the shared memory located at `/dev/shm` has been increased. See\n the [Increasing Shared Memory Size](#increasing-shared-memory-size) section\n for more details.\n - The `membarrier` system call is not blocked by Docker. See the\n [Allowing the membarrier System Call](#allowing-the-membarrier-system-call)\n for more details.\n - Make sure the kernel of your Linux distribution is up-to-date.\n\n[TimeZone]: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones\n[here]: https://bugzilla.mozilla.org/show_bug.cgi?id=1338771#c10\n[seccomp profile]: https://docs.docker.com/engine/security/seccomp/\n[latest official seccomp profile]: https://github.com/moby/moby/blob/master/profiles/seccomp/default.json\n\n## Credit\n\nhttps://github.com/jlesage/docker-firefox","has_starred","hub_user","immutable_tags_settings",{"_71":11,"_72":73},"enabled","rules",[74],".*","is_automated","permissions",{"_78":17,"_79":11,"_80":11},"read","write","admin","user","storage_size",2207565526,"orgData","recentTags",[87],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":96,"_46":135,"_136":90,"_137":29,"_138":52,"_53":139,"_140":141,"_142":123,"_143":135,"_144":62,"_145":17},"content_type","creator",10016711,"full_size",177587925,"id",165908066,"images",[97,114,120,124,130],{"_98":99,"_100":101,"_102":44,"_103":104,"_105":106,"_107":108,"_109":44,"_110":-5,"_111":112,"_59":62,"_113":-5},"architecture","amd64","digest","sha256:cecc9dffb41951d1baef21d7b5ab1fdae57e651c5125beb345b672ec0bc48a92","features","last_pulled","2026-09-27T16:11:34.38491015Z","last_pushed","2021-09-06T07:48:40Z","os","linux","os_features","os_version","size",177587819,"variant",{"_98":115,"_100":116,"_102":44,"_103":117,"_105":118,"_107":108,"_109":44,"_110":-5,"_111":119,"_59":62,"_113":-5},"arm64","sha256:507fe3a98ff999178983330f8b919616f9e90149e4199d752fb785c7fa20e2fd","2026-09-27T16:11:34.449262081Z","2021-09-06T07:48:41Z",177588860,{"_98":121,"_100":122,"_102":44,"_103":123,"_105":106,"_107":108,"_109":44,"_110":-5,"_111":92,"_59":62,"_113":-5},"386","sha256:103040f91e4f5943aa7939d994b170350d4e9aa3325aec43bec7ae38afc3a441","2026-09-27T16:11:34.591834265Z",{"_98":125,"_100":126,"_102":44,"_103":127,"_105":106,"_107":108,"_109":44,"_110":-5,"_111":128,"_59":62,"_113":129},"arm","sha256:eb9e54268018fe5ef98e019af7a104d2af061e0ef3979edca6fee7d7380df9f0","2026-09-27T16:11:34.341798138Z",177588241,"v7",{"_98":125,"_100":131,"_102":44,"_103":132,"_105":106,"_107":108,"_109":44,"_110":-5,"_111":133,"_59":62,"_113":134},"sha256:6630a0244002c2cff31d65b5cf597b409d3596a001b57747854a97bbcd8c5fe3","2026-09-27T16:11:34.358349243Z",177589611,"v6","2021-09-06T07:48:40.585323Z","last_updater","last_updater_username","media_type","master","repository",15294328,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_34":157,"_164":165,"_153":178,"_179":11},{"_36":158,"_38":159,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":160,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":161,"_75":11,"_76":163,"_81":29,"_82":83},[],[40],[52],{"_71":11,"_72":162},[74],{"_78":17,"_79":11,"_80":11},"tags",{"_166":60,"_167":-5,"_168":-5,"_169":170},"count","next","previous","results",[171],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":172,"_46":135,"_136":90,"_137":29,"_138":52,"_53":139,"_140":141,"_142":123,"_143":135,"_144":62,"_145":17},[173,174,175,176,177],{"_98":99,"_100":101,"_102":44,"_103":104,"_105":106,"_107":108,"_109":44,"_110":-5,"_111":112,"_59":62,"_113":-5},{"_98":115,"_100":116,"_102":44,"_103":117,"_105":118,"_107":108,"_109":44,"_110":-5,"_111":119,"_59":62,"_113":-5},{"_98":121,"_100":122,"_102":44,"_103":123,"_105":106,"_107":108,"_109":44,"_110":-5,"_111":92,"_59":62,"_113":-5},{"_98":125,"_100":126,"_102":44,"_103":127,"_105":106,"_107":108,"_109":44,"_110":-5,"_111":128,"_59":62,"_113":129},{"_98":125,"_100":131,"_102":44,"_103":132,"_105":106,"_107":108,"_109":44,"_110":-5,"_111":133,"_59":62,"_113":134},[],"canDeleteTags","actionData","errors"]

Digest	OS/ARCH	Compressed size
103040f91e4f	linux/386	169.36 MB
cecc9dffb419	linux/amd64	169.36 MB
6630a0244002	linux/arm/v6	169.36 MB

olivercullimore/docker-firefox

Tags for olivercullimore/docker-firefox