[{"_1":2,"_171":-5,"_172":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_150":151},"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":11},"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":85,"_104":105,"_143":-5,"_144":11,"_145":17,"_146":11,"_147":-5,"_148":149},"canonicalUrl","https://hub.docker.com/r/wingedkiwi/ubuntu-baseimage/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","wingedkiwi","reponame","ubuntu-baseimage","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":17,"_76":77,"_81":29,"_82":83},"categories",[],"content_types",[40],"image","date_registered","2015-09-10T09:50:12.490541Z","description"," A minimal Ubuntu base image that is Predictable and stays Up To Date.","is_private","last_updated","2018-04-13T23:47:28.206666Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[52],"application/vnd.docker.container.image.v1+json","name","pull_count",2999,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","# A minimal Ubuntu base image that is Predictable and stays Up To Date\n\n[![](https://badge.imagelayers.io/wingedkiwi/ubuntu-baseimage:master.svg)](https://imagelayers.io/?images=wingedkiwi/ubuntu-baseimage:master 'Get your own badge on imagelayers.io')\n\n\n_ubuntu-baseimage_ is a docker base image based on the work of [phusion/baseimage-docker](https://github.com/phusion/baseimage-docker) and inherits the following features:\n\n * [A correct Init system solving the PID 1 problem](https://blog.phusion.nl/2015/01/20/docker-and-the-pid-1-zombie-reaping-problem/).\n * Scripts in `/etc/my_init.d/` are started in lexical order.\n * `rc.local` is executed after the _Init Scripts_.\n * Fixes APT incompatibilities with Docker See https://github.com/dotcloud/docker/issues/1024.\n * A mechansim to simplify work with _Environment Variables_.\n * Provides a `cron` and `syslog-ng` with `logotate` daemon per default.\n * Ability to define additonal daemons in `/etc/service`.\n * Lightweight sudo alternative at `/sbin/setuser`\n\nMoreover _ubuntu-baseimage_ brings the following improvements:\n\n * Provides an [Automated Build](https://hub.docker.com/r/wingedkiwi/ubuntu-baseimage/) that stays up to date and\n eleminates the need to run `apt-get upgrade`. (See [dockerfile best-practices](https://docs.docker.com/articles/dockerfile_best-practices/#run))\n * Services are started in lexical order.\n * Services are terminated in reverse lexical order.\n * User command is executed after all services has been started.\n * If a `check` script for a service is provided, the init daemon will wait until service is fully started.\n * `/sbin/my_init` in `Dockerfile` is defined as `ENTRYPOINT` instead as `CMD`.\n\nChanges due to personal choice:\n\n * Removes sshd service as it is not essential (see [nsenter](https://blog.docker.com/tag/nsenter/)).\n\n_ubuntu-baseimage_ introduces backward-incompatible changes to [phusion/baseimage-docker](https://github.com/phusion/baseimage-docker).\n\n## The problems _ubuntu-baseimage_ tries to solve\n\nEven though [phusion/baseimage-docker](https://github.com/phusion/baseimage-docker) claims that it _does everything right_, it still leaves us with some unsolved problems:\n\n * The image is not updated regularly (Last push was 2 months ago, whereas _Ubuntu_ base Image was pushed 8 days ago. Status from 10th Sep 2015). Moreover it advocates the use of `apt-get upgrade` which is contrary to [dockerfile best-practices](https://docs.docker.com/articles/dockerfile_best-practices/#run))\n * Naturally services/daemons depend on each other. _phusion/baseimage-docker_ starts and stops all daemons at the same time causing unpredictable behavior and failure.\n * _phusion/baseimage-docker_ executes the user provided command without knowing if the required services/daemons are up and running.\n\n_ubuntu-baseimage_ solves the above problems using an [Automated Build](https://hub.docker.com/r/wingedkiwi/ubuntu-baseimage/) and a predictable boot and shutdown mechanism.\n\n## Using _ubuntu-baseimage_ as base image\n\n * [Getting started](#getting_started)\n * [Adding additional daemons](#adding_additional_daemons)\n * [Starting order](#starting_order)\n * [Wait until daemon is fully up](#wait_until)\n * [Disable daemons](#disable_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\n\n### Getting started\n\nThe image is called `wingedkiwi/ubuntu-baseimage`, and is available on the [Docker registry](https://hub.docker.com/r/wingedkiwi/ubuntu-baseimage/).\n\n # Use wingedkiwi/ubuntu-baseimage as base image.\n FROM wingedkiwi/ubuntu-baseimage:\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 # Run your command or leave empty if only the daemons should be started.\n CMD [\"your_command\"]\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/30-memcached\n ADD memcached.sh /etc/service/30-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#### Starting order\nDaemons are started in lexical order. System services are defined as `10-syslog-ng`, `10-syslog-forwarder` and `20-cron`, so you can define your daemons e.g. starting with 30 to start your daemon after the system services.\n\n\n#### Wait until daemon is fully up\nYou can add a `check` script to make the _Init System_ wait until daemon is fully up.\n\nExample `memcached-check.sh` file:\n\n #!/bin/bash\n if [ $memcached_is_up = true ]; then\n exit 0\n fi\n exit 1\n\nAnd in `Dockerfile`:\n\n ADD memcached-check.sh /etc/service/30-memcached/check\n\n\n### Disable Daemons\nAny daemon can be disabled by adding a `disabled` file to the corresponding service folder.\n\n RUN touch /etc/service/30-memcached/disabled\n\n\n### Running scripts during container startup\n\nThe _ubuntu-baseimage_ 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 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 wingedkiwi/ubuntu-baseimage: 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\nUpgrading inside the container would violate docker best practices. _ubuntu-baseimage_ is always kept up to date using an [Automated Build](https://hub.docker.com/r/wingedkiwi/ubuntu-baseimage/) on Docker Hub. Simply rebuild your container using this base image.\n\n","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",10292714751,"orgData",{"_86":87,"_88":89,"_90":91,"_92":29,"_93":94,"_95":94,"_96":94,"_97":94,"_98":99,"_100":94,"_101":94,"_102":94,"_103":17},"id","d6728bccdf2d4151aa3e1303ae9a237d","uuid","d6728bcc-df2d-4151-aa3e-1303ae9a237d","type","organization","orgname","full_name","","location","company","profile_url","date_joined","2015-04-02T05:33:33.279835Z","gravatar_url","gravatar_email","badge","is_active","recentTags",[106],{"_107":40,"_108":109,"_110":111,"_112":113,"_86":114,"_115":116,"_46":131,"_132":133,"_134":29,"_135":52,"_53":136,"_137":138,"_139":122,"_140":131,"_141":62,"_142":17},"content_type","creator",351223,"digest","sha256:c7e0c681beed76a4ac20d4a8de6b70b3c7d86a7e2501b412a5863251252bdca4","full_size",88981415,871382,"images",[117],{"_118":119,"_110":111,"_120":94,"_121":122,"_123":124,"_125":126,"_127":94,"_128":-5,"_129":113,"_59":62,"_130":-5},"architecture","amd64","features","last_pulled","2026-08-23T17:30:06.013144353Z","last_pushed","2018-04-13T23:47:28Z","os","linux","os_features","os_version","size","variant","2018-04-13T23:47:27.87977Z","last_updater",263232,"last_updater_username","media_type","master","repository",317621,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_34":152,"_159":160,"_148":169,"_170":11},{"_36":153,"_38":154,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":155,"_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":156,"_75":17,"_76":158,"_81":29,"_82":83},[],[40],[52],{"_71":11,"_72":157},[74],{"_78":17,"_79":11,"_80":11},"tags",{"_161":60,"_162":-5,"_163":-5,"_164":165},"count","next","previous","results",[166],{"_107":40,"_108":109,"_110":111,"_112":113,"_86":114,"_115":167,"_46":131,"_132":133,"_134":29,"_135":52,"_53":136,"_137":138,"_139":122,"_140":131,"_141":62,"_142":17},[168],{"_118":119,"_110":111,"_120":94,"_121":122,"_123":124,"_125":126,"_127":94,"_128":-5,"_129":113,"_59":62,"_130":-5},[],"canDeleteTags","actionData","errors"]

wingedkiwi/ubuntu-baseimage

Tags for wingedkiwi/ubuntu-baseimage