
Day 19 of my GSoC preparation
In this blog post, I will share my progress on the project Sugarizer, which is one of the open source projects I am interested in for Google Summer of Code (GSoC). Sugarizer is a web application that allows users to access the Sugar learning platform from any device. It is based on HTML5 and JavaScript technologies, and can run on any browser.

To work on Sugarizer, I first had to install it on Docker, which is a tool that allows developers to create, deploy, and run applications using containers. I had no prior knowledge of Docker, so I had to learn it from scratch. I followed the official documentation and some online tutorials, and learned many things like how to create images, containers, networks, volumes, and how to use docker-compose to manage multiple containers.
However, I faced one error while trying to run Sugarizer on Docker. The error message was:
failed to solve: failed to parse stage name "llaske/multiarch-mongodb:": invalid reference format
This error indicates that the docker-compose command could not understand the name of the image that I specified in the docker-compose file. This is because the image name has an invalid format, which is not allowed by Docker. I searched online for a solution, and found out that I had to change the line in the docker-compose file that says:
image: llaske/multiarch-mongodb:
to
image: llaske/multiarch-mongodb:latest
This would tell Docker to use the latest version of the image from the Docker Hub repository. I made this change, but I still encountered the same problem. I was not sure what was causing this error, so I posted it on the Sugarizer community channel and asked for help. I am still waiting for a solution from the mentors or other contributors.
That’s all I did today. Thank you for reading my blog post. I hope you learned something new from it. If you have any questions or suggestions, please leave a comment below. I will update you on my progress in the next blog post. Stay tuned!
Get the next post in your inbox.
I write when there is something genuinely useful to explain: an implementation detail, a database failure mode, or an architectural trade-off worth documenting. Zero spam.
Responses on Medium
This historical post is archived from Medium (@kumardivyanshu118). Leave claps or responses directly on the Medium story.