Retropie docker

Retropie docker DEFAULT

Installing on Windows

Download and run the installer.

Configure EmulationStation.

I wish every section was this short.

NOTE: if you choose to use the ZIP file instead, you must also install the MSVC2013 x86 redistributable.

Installing on Debian

You can either install a stable version of EmulationStation from a pre-made package, or compile the bleeding edge developer version.

Install the latest stable package.

Download and install the Debian package, either 32-bit or 64-bit.

Configure EmulationStation.

Or, compile the latest version yourself.

Make sure everything is up to date

Install dependencies

Download the latest source

Compile and install it

Installing on Raspberry Pi (RetroPie)

The RetroPie Project provides an easy way to install over 30 different emulators on the Raspberry Pi, using EmulationStation as a front-end. This is one of the easiest ways to get your Raspberry Pi ready for some retro gaming goodness.

NOTE: RetroPie is not a part of EmulationStation. If you have problems with it, report them on the RetroPie GitHub issues page. EmulationStation is only the front-end. Furthermore, the version of EmulationStation provided by RetroPie is a fork adding some RetroPie-specific customizations and features.

Installing on Raspberry Pi (Stand-alone)

This is a guide for everything you need to install EmulationStation on a fresh Raspbian Stretch install. All the dependencies are in the Raspbian apt repositories.

Make sure everything is up to date

Set the minimum amount of RAM to the GPU

Reboot to apply GPU RAM changes and make sure you're using the newest firmware

Install dependencies for EmulationStation

Compile and install EmulationStation

This will take a long time.

If you want to install emulationstation to , which will let you just type 'emulationstation' to run it, you can do:

NOTE: This will conflict with RetroPie, which installs a bash script to .

Otherwise, you can run the binary from the root of the EmulationStation folder:

Reset GPU RAM to normal values and reboot

Configure EmulationStation and install some themes.

Configuring EmulationStation

WARNING: Do not edit configuration files while EmulationStation is running. This has been known to cause strange side effects, like overwritten files and melting the polar ice caps.

If you are using a pre-configured distribution like RetroPie, you can probably skip this section.

You might want to read the file as well as this document.

The Folder

EmulationStation stores all of its configuration files relative to some "home folder." Every EmulationStation configuration file goes in a folder inside of this "home folder."

I occasionally refer to this path as . Just mentally replace the with your platform's home folder.


On Windows, the "home folder" is set by the environment variable. To see where that actually is, just type it into the Windows Explorer window and press enter:




So, the complete path to the folder is .


On Linx, this is equivalent to the environment variable. This is where your terminal and file browser should start.

So, the complete path to the folder is .

NOTE: On Linux, files and folders that start with a are "hidden folders," so the folder may not appear. If you are using the terminal, you can use to list all files in a directory, including hidden ones. If you are using a graphical interface, there should be an option to show hidden files and folders.

The File

This is the main configuration file for EmulationStation. It is located at . It is an XML document that defines a list of systems . A system contains the minimum information required to find your games and start them.

Here is an example, with comments:

Notice all s are listed inside of one tag.

If you want to add another system, just add it like so:

Systems are displayed in the order they are defined.

NOTE: If a system does not have at least one game present (that matches the extension list), it will not be displayed.
If no systems have games present, you will get an "invalid configuration" error!

Recommended Theme Names

EmulationStation will not restrict the names you pick for themes. However, in the interest of keeping installing themes a simple drag-and-drop process for everyone's setup, please use one of the following as your system's theme name:

NOTE: These are case sensitive on Linux.

(if it's not here, you are free to make something up, since a theme probably doesn't exist for it yet)

Platform Names

This is the list of valid platforms you can in a tag. The platform is used when scraping to provide more accurate results. You can use more than one platform.

NOTE: These are case sensitive.

  • - commodore 64
  • - neo geo pocket
  • - neo geo pocket color
  • - nintendo 3DS
  • - nintendo 64
  • - nintendo DS
  • - nintendo entertainment system
  • - game boy
  • - game boy advance
  • - game boy color
  • - gamecube
  • - sega genesis
  • - sega master system
  • - sega megadrive
  • - sega saturn
  • - playstation portable
  • - super nintendo entertainment system
  • - turbografx-16/pcengine
  • - do not allow scraping for this system; will remove this system from the scraping list and remove the "scrape" button in the metadata editor.

(if you suspect this is not up to date, check )

Launch Commands

Launch commands depend on what emulator you want to use.

95% of the time, or works.

If you're using MAME, should do the trick.

The following strings are replaced in your launch command:

  • - Replaced with the shell-escaped absolute path to the selected ROM. On Linux, most Bash special characters are escaped with a backslash. On Windows, the ROM path is automatically enclosed in quotes, which is equivalent to "%ROM_RAW%" (as of version 2.0.1).
  • - Replaced with the "base" name of the path to the selected ROM. For example, a path of "/foo/bar.rom", this tag would be "bar". This tag is useful for setting up MAME.
  • - Replaced with the unescaped, absolute path to the selected ROM. If your emulator is picky about paths or you are on Windows, you might want to use this instead of %ROM%, but enclosed in quotes. For example: .

Installing Themes

If you used the Windows installer or Debian package, a set of default themes should already be installed (to on Windows and on Linux).

As long as you used a name from the list above, you only need to download and extract the theme set to . If the folder doesn't already exist, just create it.

After that, select the new theme set in , like so:


That's it!

There's no dedicated Themes page on the website yet, but the official theme can be downloaded here.


Hi, have your heard about RetroPie? The most famous emulation software os Raspberry Pi. Today, I will tell you, how can you install on Raspberry Pi OS.

To follow this tutorial instructions, you will need a Raspberry Pi running Raspberry Pi OS. You can get the instructions how to install here.


Installing RetroPie

To install RetroPie, follow the steps bellow:

  1. Run the command
  2. Install the needed packages for the RetroPie
  3. Let clone RetroPie-Setup repository
  4. Lets enter on the download repository folder
  5. Let’s give permission of execution on the file
  6. Lets run the command to initialize RetroPie installation and select the option Basic Install and press Enter
  7. Choose Yes
  8. The installation will begin. This may take a while.
  9. When it finish, move the cursor selection to the right and press Enter on option Exit

RetroPie now is installed. To start RetroPie, run the command

Add ROMs on RetroPie

RetroPie on the first running will have no emulator options. To add new options, just add your ROMs on the respective folders on the path .

RetroPie ROMs Folder

Start RetroPie on boot (Optional)

If you want to start RetroPie on boot, just follow the steps on the Raspberry Pi OS terminal:

  1. Run RetroPie installation menu and choose the option Configuration / tools
  2. Select autostart option
  3. Select Start Emulation Station at boot

Using PS4 on RetroPie controller without USB Cable (Optional)

RetroPie works with all kind of USB Joystick controllers, but if you have a Playstation 4 controller, you can use in wireless mode. Follow the steps bellow to configure:

  1. On you Raspberry Pi terminal, run RetroPie installation menu using the commands and and choose the option Configuration / tools
  2. Choose option Bluetooth – Configure Bluetooth Devices and press Enter
  3. Enter you PS4 controller on paring mode holding the Share Button + PS Button for 3 seconds
  4. Choose option Register and Connect to Bluetooth Device
  5. Wait to Raspberry Pi find the PS4 controller
  6. Choose the PS4 controller
    • Look that the list does not show the device name. Turn off all bluetooth devices to show only PS4 controller.
  7. Choose the option DisplayYesNo

Uninstall RetroPie

If in the future you want to uninstall RetroPie, you can do it just selecting the option Uninstall RetroPie in the main menu

  1. On you Raspberry Pi terminal, run RetroPie installation menu using the commands and and choose the option Uninstall RetroPie
Uninstall option on RetroPie

Thats it! Now you can play your retro games with you PS4 controller without any cable. Bye!



  1. Walmart drink enhancer
  2. Antimatter dimensions discord
  3. Jasper county, iowa arrests


Building your own custom RetroPie image can be really slow, so I created a simpler way to do it using Docker and bash scripts - introducing docker-build-retropie-image!

Creating custom prebuilt images was becoming painful. I would burn the base RetroPie image to my sdcard, then I would copy any roms or BIOS over. Afterwards I would take my sdcard back and make a backup of it which created a new image I could then reuse.

So now this is my new automated flow with Docker and bash scripts:

  1. Download RetroPie image zip
  2. Extract RetroPie image
  3. Resize image to the size in GB of roms + BIOS files
  4. Mount image file so files can be copied to it
  5. Copy roms + BIOS files into image
  6. Unmount image file, its now ready for burning to an sdcard

Now the whole process is fast and simple! The solution is using Docker too so it works with MacOS, Windows and Linux.

See the docker installation guide for help installing it.

Whilst testing with Docker for Mac, deleted files from the volume were seemingly gone from both Mac and the Docker container... but not really!

For example I do in MacOS and then in the Docker container I do and I see this:

Why!? I should see instead. It might have something to do with Docker for Mac's limitations but currently I have no workaround for this.

Try this new flow out for yourself, I found I spent a lot less time copying over everything manually via SSH or USB. Now I can spend more time on getting my custom RetroPie image correct and rebuilding it very easily.

Find the GitHub project here: docker-build-retropie-image

Building the Ultimate Retro Console! Raspberry Pi 4 (8Gb) Retro Pi Tutorial


Docker retropie


64bit Monkabutu 1.0. Raspberry Pi 4 8GB. 64bit Retropie. Ubuntu Mate Desktopify version.


You will also like:


270 271 272 273 274