Troubleshooting

Troubleshooting

If you are having trouble with a build, you can of course open an issue and @vsoch and the robots will help to the best that they can. If you want to debug your own build, this is very possible! The builders use the secure build image, and you can install it locally with these two lines. Then to build locally:

sudo singularity build --isolated container.simg Singularity

A few "pro tips"

• generally don't install to the /root folder, as this might have issues when the container is executed in user space.
• it's best to put all install commands directly in the post section, as opposed to within scripts that are executed from it.

Why is my container stuck in "waiting"

When you start and stop builds quickly, such as committing to create a container, and then immediately committing again, the instance sometimes is delayed in coming down, and as a result the (equivalently named) instance is not created. This is a bug that we will fix, and in the meantime if you run into this issue you can cancel a currently running build first and then commit. If you already triggered the error, simply delete the container and build again.

Why isn't my webhook working?

For collections that were migrated (and existed on the testing server before it was converted to singularity-hub.org) the webhooks need to be updated for the different server address. The first obvious thing to try is logging out, and back in again. You can also navigate to the Settings --> Applications --> OAuth applications page and look at the configuration and response for the hook to better understand any issues. If you have no legacy images and don't mind rebuilding, then just delete the collection, log out and back in, and authenticate again. If you have legacy images (and don't want to delete the collection) then you can either make a second collection to work from, or wait for @vsoch to carefully update the webhooks.

Why don't all my commits build images?

If you are ever confused about why a build seems to be over-writing another, remember that the default behavior is to do this *unless you specify to freeze an image. Also be careful to check your build trigger settings. For example, if you are set to build manually, builds will not happen when you commit.

Where are my old images?

Don't worry! All images and metadata are still happily existing on their original server, and @vsoch will soon get working a legacy domain for this. The legacy domain will be available until the end of the calendar year.