Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

skyaware978 is 404 #112

Closed
EasternPA opened this issue Mar 1, 2022 · 1 comment · Fixed by #124
Closed

skyaware978 is 404 #112

EasternPA opened this issue Mar 1, 2022 · 1 comment · Fixed by #124
Assignees

Comments

@EasternPA
Copy link
Contributor

EasternPA commented Mar 1, 2022

I lost the skyaware978 view on the piaware container web UI when the images moved to gchr. I had to manually copy /usr/share/dump978-fa into /usr/share/skyaware978 to get it back. In https://github.com/sdr-enthusiasts/docker-baseimage/blob/main/Dockerfile.dump978-full#L41 you make the /usr/share/dump978-fa directory and copy skyaware into it, but you never make the /usr/share/skyaware978 directory.

Once I manually copied /usr/share/dump978-fa back into /usr/share/skyaware978 within the running container, the skyaware978 web UI came back no problem. I don't know what to fix in docker-baseimage to make that directory get created and populated.

@mikenye mikenye self-assigned this Mar 28, 2022
@mikenye mikenye mentioned this issue Mar 28, 2022
@mikenye
Copy link
Member

mikenye commented Mar 28, 2022

Hi @EasternPA,

I've put a fix for this in the Dockerfile (create a symlink instead of copy to keep the image size as small as possible).

Once PR #124 is merged, this issue will automatically be closed. After this, the new image will build (will take about 1-2 hours). Once complete, please pull the image and update your container.

Please feel free to re-open the issue if you're still having problems after that.

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants