Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't use webm images because the container space is to small. #812

Open
1 task done
ThomasBerne opened this issue Oct 15, 2023 · 2 comments
Open
1 task done

Can't use webm images because the container space is to small. #812

ThomasBerne opened this issue Oct 15, 2023 · 2 comments

Comments

@ThomasBerne
Copy link

Bug description

Getting this error when trying to add a webm image as background :

image

The issue is wellknown in the community : https://www.reddit.com/r/FoundryVTT/comments/10kk4co/getting_the_same_error_when_trying_to_add/

I should add more space to the container. So I added the storage_opt (https://docs.docker.com/compose/compose-file/compose-file-v2/#storage_opt) property to my container but it continues to show the bug. Here is my docker-compose.yml file :

version: "3.8"

services:
  foundry:
    image: felddy/foundryvtt:10.291
    volumes:
      - "./foundry:/data"
    ports:
      - 30000:30000/tcp
    environment:
      FOUNDRY_USERNAME: <HIDDEN>
      FOUNDRY_PASSWORD: <HIDDEN>
      CONTAINER_PRESERVE_CONFIG: "TRUE"
      FOUNDRY_LANGUAGE: "fr.fr-core"
      FOUNDRY_ADMIN_KEY: <HIDDEN>
    tty: true
    stdin_open: true
    restart: unless-stopped
    storage_opt:
      size: '20G'

Steps to reproduce

  • Create a foundry 10 container
  • Add a background image in the webm format
  • You can't apply it and the error described above is shown

Expected behavior

It should show the image with the animation.

Container metadata

com.docker.compose.config-hash = "765d994d0f7349f54eaaa023b1d24ee48856421e5b71ca242028e45b25ef4d5a"
com.docker.compose.container-number = "1"
com.docker.compose.depends_on = ""
com.docker.compose.image = "sha256:9869707a2f4a57ca24bd95aebba9f66960ad426c2fb0badc2c3f38ec28372678"
com.docker.compose.oneoff = "False"
com.docker.compose.project = "foundryvtt"
com.docker.compose.project.config_files = "/home/thomas/Documents/foundryvtt/docker-compose.yml"
com.docker.compose.project.working_dir = "/home/thomas/Documents/foundryvtt"
com.docker.compose.replace = "ad41d355e6149cdc8f706f9c570df3fb585af2c0dd7733758e27ff2ba3a0d6c5"
com.docker.compose.service = "k1nggor"
com.docker.compose.version = "2.17.3"
com.foundryvtt.version = "10.291"
org.opencontainers.image.authors = "markf+github@geekpad.com"
org.opencontainers.image.created = "2023-04-29T19:59:31.910Z"
org.opencontainers.image.description = "An easy-to-deploy Dockerized Foundry Virtual Tabletop server."
org.opencontainers.image.licenses = "MIT"
org.opencontainers.image.revision = "98271566841dbdb086bede336d8885137dcf7550"
org.opencontainers.image.source = "https://github.com/felddy/foundryvtt-docker"
org.opencontainers.image.title = "foundryvtt-docker"
org.opencontainers.image.url = "https://github.com/felddy/foundryvtt-docker"
org.opencontainers.image.vendor = "Geekpad"
org.opencontainers.image.version = "10.291.1"

Relevant log output

No errors shown in the console when the bug appears.

Code of Conduct

  • I agree to follow this project's Code of Conduct
@felddy
Copy link
Owner

felddy commented Oct 15, 2023

I'll take a look at this but my guess is that this is not a bug in the container implementation.

Possibly related:

@ThomasBerne
Copy link
Author

It looks like the storage_opt option was discontinued for docker compose 3.X.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants