[GH-ISSUE #65] Tmpfs.size invalid when running docker-compose pull #26

New issue

Closed

opened 2026-10-15 12:48:05 +00:00 by bsakaguchi · 4 comments

bsakaguchi commented

2026-10-15 12:48:05 +00:00

Owner

Originally created by @curiousblueprints on GitHub (Feb 7, 2022).
Original GitHub issue: https://github.com/games-on-whales/gow/issues/65

Ubuntu server 20.04.3 LTS
Docker Compose version v2.2.3
Docker version 20.10.12, build e91ed57

I'm following the instructions for headless Ubuntu. I receive the following error during docker-compose pull:

error while interpolating services.retroarch.volumes.[].tmpfs.size: failed to cast to expected type: strconv.ParseInt: parsing "500M": invalid syntax

If I go into the .yml file and manually edit it to "500M", it works.

Originally created by @curiousblueprints on GitHub (Feb 7, 2022). Original GitHub issue: https://github.com/games-on-whales/gow/issues/65 Ubuntu server 20.04.3 LTS Docker Compose version v2.2.3 Docker version 20.10.12, build e91ed57 I'm following the instructions for headless Ubuntu. I receive the following error during `docker-compose pull`: `error while interpolating services.retroarch.volumes.[].tmpfs.size: failed to cast to expected type: strconv.ParseInt: parsing "500M": invalid syntax` If I go into the .yml file and manually edit it to "500M", it works.

bsakaguchi

2026-10-15 12:48:05 +00:00

closed this issue
added the
good first issue

bug
labels

bsakaguchi commented

2026-10-15 12:48:06 +00:00

Author

Owner

@zb140 commented on GitHub (May 8, 2022):

Apparently the magic that automatically turns 500M into 524288000 happens before variable interpolation... I also tried changing the SHM_SIZE in the .env file to just 500 and putting size: "${SHM_SIZE}M" in docker-compose.yml but that didn't work either 😦 . I guess if we want it to be a variable we're going to just have to put an integer number of bytes in .env.

@zb140 commented on GitHub (May 8, 2022): Apparently the magic that automatically turns `500M` into `524288000` happens _before_ variable interpolation... I also tried changing the `SHM_SIZE` in the `.env` file to just `500` and putting `size: "${SHM_SIZE}M"` in `docker-compose.yml` but that didn't work either 😦 . I guess if we want it to be a variable we're going to just have to put an integer number of bytes in `.env`.

bsakaguchi commented

2026-10-15 12:48:06 +00:00

Author

Owner

@ABeltramo commented on GitHub (May 8, 2022):

I guess this changed on docker-compose v2. We can safely remove that from the .env file if it's causing troubles since it's such a low level detail that probably no one will ever modify.

@ABeltramo commented on GitHub (May 8, 2022): I guess this changed on docker-compose v2. We can safely remove that from the .env file if it's causing troubles since it's such a low level detail that probably no one will ever modify.

bsakaguchi commented

2026-10-15 12:48:07 +00:00

Author

Owner

@zb140 commented on GitHub (Jul 30, 2022):

This may be fixed now, with the newest docker-compose. I'm using v2.5.0 and I no longer get the error.

@zb140 commented on GitHub (Jul 30, 2022): This may be fixed now, with the newest `docker-compose`. I'm using v2.5.0 and I no longer get the error.

bsakaguchi commented

2026-10-15 12:48:07 +00:00

Author

Owner

@zb140 commented on GitHub (Sep 4, 2022):

I'm going to go ahead and close this -- now that we've added the run-gow script and switched to docker compose v2, we're still not seeing this error anymore. If anyone runs into it again, please reopen.

@zb140 commented on GitHub (Sep 4, 2022): I'm going to go ahead and close this -- now that we've added the `run-gow` script and switched to docker compose v2, we're still not seeing this error anymore. If anyone runs into it again, please reopen.

bsakaguchi referenced this issue

2026-10-15 12:49:11 +00:00

[PR #26] [MERGED] Fix permissions for input devices #110