Building a new package does not use intermediate images about subuser HOT 3 OPEN

Subuser is configured to rebuild everything when it builds an image. Otherwise, the images that were built would be out of date. For testing when creating a package, it is therefore better to use a dev subuser.

Run this command in the repository:

subuser dev --update electrum-base

The --update flag will tell subuser to use the docker image cache while building the image, and therefore, only steps which have changed or which previously failed will be rebuilt.

It is also possible to pass the --use-cache option to subuser update in order to get the same effect with non-dev subusers.

As for being able to play with images and test build steps, the best way to do this in my opinion would be to run subuser describe subuser <subuser-name> and looking at the Docker image Id: and using docker directly. Another option, if the image doesn't build correctly at all, would be to run a command like this cat ~/.subuser/registry/commit_log | grep -n2 "\-\-\->" | tail -n 15 and look for a line that starts with --->.

Here is some example output:

662502-Step 2/2 : RUN mkdir -p /subuser ; echo bb11cd5f-b55e-4701-b30f-612b9ecaac70 > /subuser/uuid
662503: ---> Running in b64650ea1b10
662504: ---> 614dd19b49b9
662505-Removing intermediate container b64650ea1b10

I can now issue docker run -it 614dd19b49b9 bash in order to enter that layer as root.

Hope this helps,
Tim

from subuser.

It probably depends on the fact that I am using the following base image

FROM-SUBUSER-IMAGE libx11@default

which uses apt-get update and apt-get upgrade.

from subuser.

Hi @timthelion, thanks for the info, I will look into them.

I also think that this could be useful information to put in the tutorial on packaging.

from subuser.