You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to the instructions, after running add_bespoke_images.py, which copies thumbnail images into static/FinalOutputs/img/1/xxx, I should be able to do
to save a docker image with these thumbnails in the right dir. However, when I do this, and re-run the new image with docker run -v -p 8080:80 onezoom/oztree-bespoke-images-with-iucn all the images in static/FinalOutputs/img are gone. You can verify this by creating a directory by hand within the docker image in e.g. static/FinalOutputs/ then running the docker commit command. When the committed container is restarted, it won't have the hand-created directory.
I'm sure I'm misunderstanding how docker commit works here. I wonder if @lentinj has any clue what I should be doing to persist a user's local changes in a new docker container in an easy way.
The text was updated successfully, but these errors were encountered:
It's not something I've used before, but reading the docs it does sound like it should do what you want it to.
Another option would be to have an external volume for ICUN image storage, which the docker image can populate if it isn't already. That seems like it's the more docker-ish way to do it anyway.
According to the instructions, after running
add_bespoke_images.py
, which copies thumbnail images intostatic/FinalOutputs/img/1/xxx
, I should be able to doto save a docker image with these thumbnails in the right dir. However, when I do this, and re-run the new image with
docker run -v -p 8080:80 onezoom/oztree-bespoke-images-with-iucn
all the images instatic/FinalOutputs/img
are gone. You can verify this by creating a directory by hand within the docker image in e.g.static/FinalOutputs/
then running thedocker commit
command. When the committed container is restarted, it won't have the hand-created directory.I'm sure I'm misunderstanding how
docker commit
works here. I wonder if @lentinj has any clue what I should be doing to persist a user's local changes in a new docker container in an easy way.The text was updated successfully, but these errors were encountered: