[{"_1":2,"_161":-5,"_162":-5},"loaderData",{"_3":4,"_17":18,"_25":26,"_140":141},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7,"_13":14,"_15":16},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","theme","system","contrast","normal","routes/_layout",{"_19":-5,"_20":21,"_22":21,"_23":11,"_24":21},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_27":28,"_29":-5,"_30":11,"_31":11,"_32":33,"_34":35,"_36":-5,"_37":11,"_38":39,"_88":-5,"_89":90,"_129":-5,"_130":11,"_131":21,"_132":11,"_133":-5,"_134":11,"_135":-5,"_136":137,"_138":91,"_139":-7},"canonicalUrl","https://hub.docker.com/r/petronetto/ubuntu/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","petronetto","reponame","ubuntu","cloudBuildSource","isAutobuildsAvailable","repo",{"_40":41,"_42":43,"_45":46,"_47":48,"_49":11,"_50":51,"_52":53,"_54":55,"_57":35,"_32":33,"_58":59,"_60":-5,"_61":62,"_63":62,"_64":65,"_66":-5,"_67":68,"_69":70,"_71":11,"_72":33,"_73":74,"_79":21,"_80":81,"_85":33,"_86":87},"categories",[],"content_types",[44],"image","date_registered","2016-11-10T02:16:04.925001Z","description","A minimal Ubuntu base image modified for Docker-friendliness","is_private","last_updated","2016-11-10T02:56:21.171653Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[56],"application/vnd.docker.container.image.v1+json","name","pull_count",329,"repository_type","star_count",1,"status","status_description","active","source","collaborator_count",0,"full_description","# A minimal Ubuntu base image modified for Docker-friendliness\n\n[![](https://badge.imagelayers.io/phusion/baseimage:0.9.17.svg)](https://imagelayers.io/?images=phusion/baseimage:latest 'Get your own badge on imagelayers.io')\n\n_Baseimage-docker only consumes 6 MB RAM and is much powerful than Busybox or Alpine. See why below._\n\nBaseimage-docker is a special [Docker](https://www.docker.com) image that is configured for correct use within Docker containers. It is Ubuntu, plus:\n\n * Modifications for Docker-friendliness.\n * Administration tools that are especially useful in the context of Docker.\n * Mechanisms for easily running multiple processes, [without violating the Docker philosophy](#docker_single_process).\n\nYou can use it as a base for your own Docker images.\n\nBaseimage-docker is available for pulling from [the Docker registry](https://registry.hub.docker.com/u/phusion/baseimage/)!\n\n### What are the problems with the stock Ubuntu base image?\n\nUbuntu is not designed to be run inside Docker. Its init system, Upstart, assumes that it's running on either real hardware or virtualized hardware, but not inside a Docker container. But inside a container you don't want a full system anyway, you want a minimal system. But configuring that minimal system for use within a container has many strange corner cases that are hard to get right if you are not intimately familiar with the Unix system model. This can cause a lot of strange problems.\n\nBaseimage-docker gets everything right. The \"Contents\" section describes all the things that it modifies.\n\n\n### Why use baseimage-docker?\n\nYou can configure the stock `ubuntu` image yourself from your Dockerfile, so why bother using baseimage-docker?\n\n * Configuring the base system for Docker-friendliness is no easy task. As stated before, there are many corner cases. By the time that you've gotten all that right, you've reinvented baseimage-docker. Using baseimage-docker will save you from this effort.\n * It reduces the time needed to write a correct Dockerfile. You won't have to worry about the base system and can focus on your stack and your app.\n * It reduces the time needed to run `docker build`, allowing you to iterate your Dockerfile more quickly.\n * It reduces download time during redeploys. Docker only needs to download the base image once: during the first deploy. On every subsequent deploys, only the changes you make on top of the base image are downloaded.\n\n-----------------------------------------\n\n**Related resources**:\n [Website](http://phusion.github.io/baseimage-docker/) |\n [Github](https://github.com/phusion/baseimage-docker) |\n [Docker registry](https://index.docker.io/u/phusion/baseimage/) |\n [Discussion forum](https://groups.google.com/d/forum/passenger-docker) |\n [Twitter](https://twitter.com/phusion_nl) |\n [Blog](http://blog.phusion.nl/)\n\n**Table of contents**\n\n * [What's inside the image?](#whats_inside)\n * [Overview](#whats_inside_overview)\n * [Wait, I thought Docker is about running a single process in a container?](#docker_single_process)\n * [Does Baseimage-docker advocate \"fat containers\" or \"treating containers as VMs\"?](#fat_containers)\n * [Inspecting baseimage-docker](#inspecting)\n * [Using baseimage-docker as base image](#using)\n * [Getting started](#getting_started)\n * [Adding additional daemons](#adding_additional_daemons)\n * [Running scripts during container startup](#running_startup_scripts)\n * [Environment variables](#environment_variables)\n * [Centrally defining your own environment variables](#envvar_central_definition)\n * [Environment variable dumps](#envvar_dumps)\n * [Modifying environment variables](#modifying_envvars)\n * [Security](#envvar_security)\n * [Upgrading the operating system inside the container](#upgrading_os)\n * [Container administration](#container_administration)\n * [Running a one-shot command in a new container](#oneshot)\n * [Running a command in an existing, running container](#run_inside_existing_container)\n * [Login to the container via `docker exec`](#login_docker_exec)\n * [Usage](#docker_exec)\n * [Login to the container via SSH](#login_ssh)\n * [Enabling SSH](#enabling_ssh)\n * [About SSH keys](#ssh_keys)\n * [Using the insecure key for one container only](#using_the_insecure_key_for_one_container_only)\n * [Enabling the insecure key permanently](#enabling_the_insecure_key_permanently)\n * [Using your own key](#using_your_own_key)\n * [The `docker-ssh` tool](#docker_ssh)\n * [Building the image yourself](#building)\n * [Removing optional services](#removing_optional_services)\n * [Conclusion](#conclusion)\n\n-----------------------------------------\n\n\n## What's inside the image?\n\n\n### Overview\n\n*Looking for a more complete base image, one that is ideal for Ruby, Python, Node.js and Meteor web apps? Take a look at [passenger-docker](https://github.com/phusion/passenger-docker).*\n\n| Component | Why is it included? / Remarks |\n| ---------------- | ------------------- |\n| Ubuntu 16.04 LTS | The base system. |\n| A **correct** init process | _Main article: [Docker and the PID 1 zombie reaping problem](http://blog.phusion.nl/2015/01/20/docker-and-the-pid-1-zombie-reaping-problem/)._

According to the Unix process model, [the init process](https://en.wikipedia.org/wiki/Init) -- PID 1 -- inherits all [orphaned child processes](https://en.wikipedia.org/wiki/Orphan_process) and must [reap them](https://en.wikipedia.org/wiki/Wait_(system_call)). Most Docker containers do not have an init process that does this correctly, and as a result their containers become filled with [zombie processes](https://en.wikipedia.org/wiki/Zombie_process) over time.

Furthermore, `docker stop` sends SIGTERM to the init process, which is then supposed to stop all services. Unfortunately most init systems don't do this correctly within Docker since they're built for hardware shutdowns instead. This causes processes to be hard killed with SIGKILL, which doesn't give them a chance to correctly deinitialize things. This can cause file corruption.

Baseimage-docker comes with an init process `/sbin/my_init` that performs both of these tasks correctly. |\n| Fixes APT incompatibilities with Docker | See https://github.com/dotcloud/docker/issues/1024. |\n| syslog-ng | A syslog daemon is necessary so that many services - including the kernel itself - can correctly log to /var/log/syslog. If no syslog daemon is running, a lot of important messages are silently swallowed.

Only listens locally. All syslog messages are forwarded to \"docker logs\". |\n| logrotate | Rotates and compresses logs on a regular basis. |\n| SSH server | Allows you to easily login to your container to [inspect or administer](#login_ssh) things.

_SSH is **disabled by default** and is only one of the methods provided by baseimage-docker for this purpose. The other method is through [docker exec](#login_docker_exec). SSH is also provided as an alternative because `docker exec` comes with several caveats._

Password and challenge-response authentication are disabled by default. Only key authentication is allowed. |\n| cron | The cron daemon must be running for cron jobs to work. |\n| [runit](http://smarden.org/runit/) | Replaces Ubuntu's Upstart. Used for service supervision and management. Much easier to use than SysV init and supports restarting daemons when they crash. Much easier to use and more lightweight than Upstart. |\n| `setuser` | A tool for running a command as another user. Easier to use than `su`, has a smaller attack vector than `sudo`, and unlike `chpst` this tool sets `$HOME` correctly. Available as `/sbin/setuser`. |\n\nBaseimage-docker is very lightweight: it only consumes 6 MB of memory.\n\n\n### Wait, I thought Docker is about running a single process in a container?\n\nThe Docker developers advocate the philosophy of running a single *logical service* per container. A logical service can consist of multiple OS processes.\n\nBaseimage-docker only advocates running multiple OS processes inside a single container. We believe this makes sense because at the very least it would solve [the PID 1 problem](http://blog.phusion.nl/2015/01/20/docker-and-the-pid-1-zombie-reaping-problem/) and the \"syslog blackhole\" problem. By running multiple processes, we solve very real Unix OS-level problems, with minimal overhead and without turning the container into multiple logical services.\n\nSplitting your logical service into multiple OS processes also makes sense from a security standpoint. By running processes as different users, you can limit the impact of vulnerabilities. Baseimage-docker provides tools to encourage running processes as different users, e.g. the `setuser` tool.\n\nDo we advocate running multiple *logical services* in a single container? Not necessarily, but we do not prohibit it either. While the Docker developers are very opinionated and have very rigid philosophies about how containers *should* be built, Baseimage-docker is completely unopinionated. We believe in freedom: sometimes it makes sense to run multiple services in a single container, and sometimes it doesn't. It is up to you to decide what makes sense, not the Docker developers.\n\n\n### Does Baseimage-docker advocate \"fat containers\" or \"treating containers as VMs\"?\n\nThere are people who are under the impression that Baseimage-docker advocates treating containers as VMs, because of the fact that Baseimage-docker advocates the use of multiple processes. Therefore they are also under the impression that Baseimage-docker does not follow the Docker philosophy. Neither of these impressions are true.\n\nThe Docker developers advocate running a single *logical service* inside a single container. But we are not disputing that. Baseimage-docker advocates running multiple *OS processes* inside a single container, and a single logical service can consist of multiple OS processes.\n\nIt follows from this that Baseimage-docker also does not deny the Docker philosophy. In fact, many of the modifications we introduce are explicitly in line with the Docker philosophy. For example, using environment variables to pass parameters to containers is very much the \"Docker way\", and provide [a mechanism to easily work with environment variables](#environment_variables) in the presence of multiple processes that may run as different users.\n\n\n## Inspecting baseimage-docker\n\nTo look around in the image, run:\n\n docker run --rm -t -i phusion/baseimage: /sbin/my_init -- bash -l\n\nwhere `` is [one of the baseimage-docker version numbers](https://github.com/phusion/baseimage-docker/blob/master/Changelog.md).\n\nYou don't have to download anything manually. The above command will automatically pull the baseimage-docker image from the Docker registry.\n\n\n## Using baseimage-docker as base image\n\n\n### Getting started\n\nThe image is called `phusion/baseimage`, and is available on the Docker registry.\n\n # Use phusion/baseimage as base image. To make your builds reproducible, make\n # sure you lock down to a specific version, not to `latest`!\n # See https://github.com/phusion/baseimage-docker/blob/master/Changelog.md for\n # a list of version numbers.\n FROM phusion/baseimage:\n\n # Use baseimage-docker's init system.\n CMD [\"/sbin/my_init\"]\n\n # ...put your own build instructions here...\n\n # Clean up APT when done.\n RUN apt-get clean && rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/*\n\n\n### Adding additional daemons\n\nYou can add additional daemons (e.g. your own app) to the image by creating runit entries. You only have to write a small shell script which runs your daemon, and runit will keep it up and running for you, restarting it when it crashes, etc.\n\nThe shell script must be called `run`, must be executable, and is to be placed in the directory `/etc/service/`.\n\nHere's an example showing you how a memcached server runit entry can be made.\n\nIn `memcached.sh` (make sure this file is chmod +x):\n\n #!/bin/sh\n # `/sbin/setuser memcache` runs the given command as the user `memcache`.\n # If you omit that part, the command will be run as root.\n exec /sbin/setuser memcache /usr/bin/memcached >>/var/log/memcached.log 2>&1\n\nIn `Dockerfile`:\n\n RUN mkdir /etc/service/memcached\n ADD memcached.sh /etc/service/memcached/run\n\nNote that the shell script must run the daemon **without letting it daemonize/fork it**. Usually, daemons provide a command line flag or a config file option for that.\n\n\n### Running scripts during container startup\n\nThe baseimage-docker init system, `/sbin/my_init`, runs the following scripts during startup, in the following order:\n\n * All executable scripts in `/etc/my_init.d`, if this directory exists. The scripts are run in lexicographic order.\n * The script `/etc/rc.local`, if this file exists.\n\nAll scripts must exit correctly, e.g. with exit code 0. If any script exits with a non-zero exit code, the booting will fail.\n\nThe following example shows how you can add a startup script. This script simply logs the time of boot to the file /tmp/boottime.txt.\n\nIn `logtime.sh` (make sure this file is chmod +x):\n\n #!/bin/sh\n date > /tmp/boottime.txt\n\nIn `Dockerfile`:\n\n RUN mkdir -p /etc/my_init.d\n ADD logtime.sh /etc/my_init.d/logtime.sh\n\n\n### Environment variables\n\nIf you use `/sbin/my_init` as the main container command, then any environment variables set with `docker run --env` or with the `ENV` command in the Dockerfile, will be picked up by `my_init`. These variables will also be passed to all child processes, including `/etc/my_init.d` startup scripts, Runit and Runit-managed services. There are however a few caveats you should be aware of:\n\n * Environment variables on Unix are inherited on a per-process basis. This means that it is generally not possible for a child process to change the environment variables of other processes.\n * Because of the aforementioned point, there is no good central place for defining environment variables for all applications and services. Debian has the `/etc/environment` file but it only works in some situations.\n * Some services change environment variables for child processes. Nginx is one such example: it removes all environment variables unless you explicitly instruct it to retain them through the `env` configuration option. If you host any applications on Nginx (e.g. using the [passenger-docker](https://github.com/phusion/passenger-docker) image, or using Phusion Passenger in your own image) then they will not see the environment variables that were originally passed by Docker.\n\n`my_init` provides a solution for all these caveats.\n\n\n#### Centrally defining your own environment variables\n\nDuring startup, before running any [startup scripts](#running_startup_scripts), `my_init` imports environment variables from the directory `/etc/container_environment`. This directory contains files who are named after the environment variable names. The file contents contain the environment variable values. This directory is therefore a good place to centrally define your own environment variables, which will be inherited by all startup scripts and Runit services.\n\nFor example, here's how you can define an environment variable from your Dockerfile:\n\n RUN echo Apachai Hopachai > /etc/container_environment/MY_NAME\n\nYou can verify that it works, as follows:\n\n $ docker run -t -i /sbin/my_init -- bash -l\n ...\n *** Running bash -l...\n # echo $MY_NAME\n Apachai Hopachai\n\n**Handling newlines**\n\nIf you've looked carefully, you'll notice that the 'echo' command actually prints a newline. Why does $MY_NAME not contain a newline then? It's because `my_init` strips the trailing newline, if any. If you intended on the value having a newline, you should add *another* newline, like this:\n\n RUN echo -e \"Apachai Hopachai\\n\" > /etc/container_environment/MY_NAME\n\n\n#### Environment variable dumps\n\nWhile the previously mentioned mechanism is good for centrally defining environment variables, it by itself does not prevent services (e.g. Nginx) from changing and resetting environment variables from child processes. However, the `my_init` mechanism does make it easy for you to query what the original environment variables are.\n\nDuring startup, right after importing environment variables from `/etc/container_environment`, `my_init` will dump all its environment variables (that is, all variables imported from `container_environment`, as well as all variables it picked up from `docker run --env`) to the following locations, in the following formats:\n\n * `/etc/container_environment`\n * `/etc/container_environment.sh` - a dump of the environment variables in Bash format. You can source the file directly from a Bash shell script.\n * `/etc/container_environment.json` - a dump of the environment variables in JSON format.\n\nThe multiple formats makes it easy for you to query the original environment variables no matter which language your scripts/apps are written in.\n\nHere is an example shell session showing you how the dumps look like:\n\n $ docker run -t -i \\\n --env FOO=bar --env HELLO='my beautiful world' \\\n phusion/baseimage: /sbin/my_init -- \\\n bash -l\n ...\n *** Running bash -l...\n # ls /etc/container_environment\n FOO HELLO HOME HOSTNAME PATH TERM container\n # cat /etc/container_environment/HELLO; echo\n my beautiful world\n # cat /etc/container_environment.json; echo\n {\"TERM\": \"xterm\", \"container\": \"lxc\", \"HOSTNAME\": \"f45449f06950\", \"HOME\": \"/root\", \"PATH\": \"/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin\", \"FOO\": \"bar\", \"HELLO\": \"my beautiful world\"}\n # source /etc/container_environment.sh\n # echo $HELLO\n my beautiful world\n\n\n#### Modifying environment variables\n\nIt is even possible to modify the environment variables in `my_init` (and therefore the environment variables in all child processes that are spawned after that point in time), by altering the files in `/etc/container_environment`. After each time `my_init` runs a [startup script](#running_startup_scripts), it resets its own environment variables to the state in `/etc/container_environment`, and re-dumps the new environment variables to `container_environment.sh` and `container_environment.json`.\n\nBut note that:\n\n * modifying `container_environment.sh` and `container_environment.json` has no effect.\n * Runit services cannot modify the environment like that. `my_init` only activates changes in `/etc/container_environment` when running startup scripts.\n\n\n#### Security\n\nBecause environment variables can potentially contain sensitive information, `/etc/container_environment` and its Bash and JSON dumps are by default owned by root, and accessible only by the `docker_env` group (so that any user added this group will have these variables automatically loaded).\n\nIf you are sure that your environment variables don't contain sensitive data, then you can also relax the permissions on that directory and those files by making them world-readable:\n\n RUN chmod 755 /etc/container_environment\n RUN chmod 644 /etc/container_environment.sh /etc/container_environment.json\n\n\n### Upgrading the operating system inside the container\n\nBaseimage-docker images contain an Ubuntu 16.04 operating system. You may want to update this OS from time to time, for example to pull in the latest security updates. OpenSSL is a notorious example. Vulnerabilities are discovered in OpenSSL on a regular basis, so you should keep OpenSSL up-to-date as much as you can.\n\nWhile we release Baseimage-docker images with the latest OS updates from time to time, you do not have to rely on us. You can update the OS inside Baseimage-docker images yourself, and it is recommend that you do this instead of waiting for us.\n\nTo upgrade the OS in the image, run this in your Dockerfile:\n\n RUN apt-get update && apt-get upgrade -y -o Dpkg::Options::=\"--force-confold\"\n\n\n## Container administration\n\nOne of the ideas behind Docker is that containers should be stateless, easily restartable, and behave like a black box. However, you may occasionally encounter situations where you want to login to a container, or to run a command inside a container, for development, inspection and debugging purposes. This section describes how you can administer the container for those purposes.\n\n\n### Running a one-shot command in a new container\n\n_**Note:** This section describes how to run a command insider a -new- container. To run a command inside an existing running container, see [Running a command in an existing, running container](#run_inside_existing_container)._\n\nNormally, when you want to create a new container in order to run a single command inside it, and immediately exit after the command exits, you invoke Docker like this:\n\n docker run YOUR_IMAGE COMMAND ARGUMENTS...\n\nHowever the downside of this approach is that the init system is not started. That is, while invoking `COMMAND`, important daemons such as cron and syslog are not running. Also, orphaned child processes are not properly reaped, because `COMMAND` is PID 1.\n\nBaseimage-docker provides a facility to run a single one-shot command, while solving all of the aforementioned problems. Run a single command in the following manner:\n\n docker run YOUR_IMAGE /sbin/my_init -- COMMAND ARGUMENTS ...\n\nThis will perform the following:\n\n * Runs all system startup files, such as /etc/my_init.d/* and /etc/rc.local.\n * Starts all runit services.\n * Runs the specified command.\n * When the specified command exits, stops all runit services.\n\nFor example:\n\n $ docker run phusion/baseimage: /sbin/my_init -- ls\n *** Running /etc/rc.local...\n *** Booting runit daemon...\n *** Runit started as PID 80\n *** Running ls...\n bin boot dev etc home image lib lib64 media mnt opt proc root run sbin selinux srv sys tmp usr var\n *** ls exited with exit code 0.\n *** Shutting down runit daemon (PID 80)...\n *** Killing all processes...\n\nYou may find that the default invocation is too noisy. Or perhaps you don't want to run the startup files. You can customize all this by passing arguments to `my_init`. Invoke `docker run YOUR_IMAGE /sbin/my_init --help` for more information.\n\nThe following example runs `ls` without running the startup files and with less messages, while running all runit services:\n\n $ docker run phusion/baseimage: /sbin/my_init --skip-startup-files --quiet -- ls\n bin boot dev etc home image lib lib64 media mnt opt proc root run sbin selinux srv sys tmp usr var\n\n\n### Running a command in an existing, running container\n\nThere are two ways to run a command inside an existing, running container.\n\n * Through the `docker exec` tool. This is builtin Docker tool, available since Docker 1.4. Internally, it uses Linux kernel system calls in order to execute a command within the context of a container. Learn more in [Login to the container, or running a command inside it, via `docker exec`](#login_docker_exec).\n * Through SSH. This approach requires running an SSH daemon inside the container, and requires you to setup SSH keys. Learn more in [Login to the container, or running a command inside it, via SSH](#login_ssh).\n\nBoth way have their own pros and cons, which you can learn in their respective subsections.\n\n\n### Login to the container, or running a command inside it, via `docker exec`\n\nYou can use the `docker exec` tool on the Docker host OS to login to any container that is based on baseimage-docker. You can also use it to run a command inside a running container. `docker exec` works by using Linux kernel system calls.\n\nHere's how it compares to [using SSH to login to the container or to run a command inside it](#login_ssh):\n\n * Pros\n * Does not require running an SSH daemon inside the container.\n * Does not require setting up SSH keys.\n * Works on any container, even containers not based on baseimage-docker.\n * Cons\n * If the `docker exec` process on the host is terminated by a signal (e.g. with the `kill` command or even with Ctrl-C), then the command that is executed by `docker exec` is *not* killed and cleaned up. You will either have to do that manually, or you have to run `docker exec` with `-t -i`.\n * Requires privi","has_starred","hub_user","immutable_tags_settings",{"_75":11,"_76":77},"enabled","rules",[78],".*","is_automated","permissions",{"_82":21,"_83":11,"_84":11},"read","write","admin","user","storage_size",151869741,"orgData","recentTags",[91],{"_92":44,"_93":94,"_95":96,"_97":98,"_99":100,"_50":118,"_119":94,"_120":33,"_121":56,"_57":122,"_123":124,"_125":109,"_126":118,"_127":65,"_128":21},"content_type","creator",946324,"full_size",100864497,"id",6020473,"images",[101],{"_102":103,"_104":105,"_106":107,"_108":109,"_110":111,"_112":113,"_114":107,"_115":-5,"_116":96,"_63":65,"_117":-5},"architecture","amd64","digest","sha256:822f584eedecd589e2255202e33d561ec16b4bf0917a8e22f5a2bd506aa4f84a","features","","last_pulled","2026-09-22T20:45:39.517543952Z","last_pushed","2016-11-10T02:56:20Z","os","linux","os_features","os_version","size","variant","2016-11-10T02:56:19.887269Z","last_updater","last_updater_username","media_type","latest","repository",1036532,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"selectedTag","attestationsUrl","routes/_layout.r.$namespace.$reponame.tags",{"_38":142,"_149":150,"_136":159,"_160":11},{"_40":143,"_42":144,"_45":46,"_47":48,"_49":11,"_50":51,"_52":53,"_54":145,"_57":35,"_32":33,"_58":59,"_60":-5,"_61":62,"_63":62,"_64":65,"_66":-5,"_67":68,"_69":70,"_71":11,"_72":33,"_73":146,"_79":21,"_80":148,"_85":33,"_86":87},[],[44],[56],{"_75":11,"_76":147},[78],{"_82":21,"_83":11,"_84":11},"tags",{"_151":62,"_152":-5,"_153":-5,"_154":155},"count","next","previous","results",[156],{"_92":44,"_93":94,"_95":96,"_97":98,"_99":157,"_50":118,"_119":94,"_120":33,"_121":56,"_57":122,"_123":124,"_125":109,"_126":118,"_127":65,"_128":21},[158],{"_102":103,"_104":105,"_106":107,"_108":109,"_110":111,"_112":113,"_114":107,"_115":-5,"_116":96,"_63":65,"_117":-5},[],"canDeleteTags","actionData","errors"]

petronetto/ubuntu

Tags for petronetto/ubuntu