Misago
  • Threads
  • Categories
  • Users
  • forum
  • group
  • search
  1. Threads
  2. Problems and issues
chevron_left Problems and issues

Error starting dev server using docker

  • forum 5 replies
  • last reply by einarf Sept. 6, 2018
  • Last
  • link
    arockiaraj1994
    Members 2 posts
    June 22, 2018, 2:08 p.m. June 22, 2018, 2:08 p.m.
    link

    Showing following errors for while docker build

    Unable to locate package libopenjpeg-dev

    ModuleNotFoundError: No module named 'misago.admin.forms'

  • link
    einarf
    Devs & Contributors 23 posts
    June 22, 2018, 6:06 p.m. June 22, 2018, 6:06 p.m.
    link

    Need a bit more info here. At least what branch you are using.

    Edit: I suspect you are using master branch. I'm guessing 0.18.x or 0.19.x is more relevant.

    Another reason for this happening is that you have an old python:3 docker image. Try adding --pull parameter the build command to override local cache. This is related to this commit in master.

  • link
    rafalp
    Project Lead 1176 posts
    Aug. 19, 2018, 3:18 p.m. Aug. 19, 2018, 3:18 p.m.
    link

    I've did complete system purge on my Docker recently and can confirm that libopenjpeg-dev is gone. Cherry-picking the new lib from linked commit fixed it for me. ;)

  • link
    einarf
    Devs & Contributors 23 posts
    Sept. 5, 2018, 4:05 p.m. Sept. 5, 2018, 4:05 p.m.
    link

    Looks like this is related to python images now using debian 9. I guess it's always a good idea to use the --pull parameter when building the compose setup to ensure no stale base images are used.

  • link
    rafalp
    Project Lead 1176 posts
    Sept. 5, 2018, 7:40 p.m. Sept. 5, 2018, 7:40 p.m.
    link

    I guess in ./dev init script we should do docker-compose build --pull --force-rm to catch those sooner?

  • link
    einarf
    Devs & Contributors 23 posts
    Sept. 6, 2018, 12:14 a.m. Sept. 6, 2018, 12:14 a.m.
    link
    @rafalp has written:

    I guess in ./dev init script we should do docker-compose build --pull --force-rm to catch those sooner?

    Probably not a bad idea. Then docker will check if there are new images available for the image tag. The same python:3.6 image will normally be built more than once because its base images also change. For example when the debian image gets a security fix.

There are no more posts in this thread.

  • This site uses cookies to gather statistical data for use in traffic analysis.
  • Terms of service
  • Privacy policy
powered by misago