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

local assets aren't used - correct / default path missing from README #24

Open
danboid opened this issue Jun 13, 2022 · 7 comments
Open

Comments

@danboid
Copy link
Contributor

danboid commented Jun 13, 2022

I have set up a local instance of netboot.xyz 2.0.59 under Ubuntu 22.04.

I have used its web interface to download all of the assets for a couple of distros. They seemed to download fine but netboot doesn't utilise them, it still downloads them from the internet every time.

I presume this is because I haven't configured the assets path correctly when I was setting up the container. What is the correct default assets path to use when setting up the container? We should add this path to the netboot.xyz docker container docs.

@danboid
Copy link
Contributor Author

danboid commented Jun 13, 2022

I looks like the default asset path should be set to /assets/asset-mirror/releases/download or maybe it should be just /assets?

@danboid
Copy link
Contributor Author

danboid commented Jun 14, 2022

I don't know how local assets are supposed to work. When I originally set up the container, I used this command:

docker run -d --name=netbootxyz -p 3000:3000 -p 69:69/udp -p 8080:80 -v /etc/netbootxyz/config:/config -v /etc/netbootxyz/assets:/assets --restart unless-stopped ghcr.io/netbootxyz/netbootxyz

I used that because I was wanting to mount a local dir ( /etc/netbootxyz/assets) in my container. It didn't seem to do that but the netboot webapp is accessible after running it. If I don't pass any -v options, I cannot access the containers web app but supposedly the -v arguments for setting asset and config dir mappings are optional?

@danboid
Copy link
Contributor Author

danboid commented Jun 14, 2022

Here's how my netboot web app asset management page looks:

netboot-assets

I'm a bit confused by the layout of the right column. At the top it says 'Untracked assets' then immediately below that it lists the assets I downloaded. I would've expected that if I could see the assets in that list then my netboot server would use those instead of downloading them right? That's not happening but are these actually still 'untracked assets' or not? The untracked assets column heading is confusing because it looks like it is an empty list followed by another separate list of tracked assets but squashed into the same column. Is that what is being displayed here?

If those local assets are downloaded but untracked, how do I make them tracked? Conversely, it it possible to make tracked assets untracked? I'm not even sure what tracked means in this case? Is it just a synonym for 'downloaded and locally hosted'?

@danboid
Copy link
Contributor Author

danboid commented Oct 20, 2022

Have you had time to look at fixing this yet @antonym ?

@DarkAxi0m
Copy link

DarkAxi0m commented Nov 18, 2023

I know this is old, but by chance if found the key point to getting local assets working.

On dashboard, edit boot.cfg, and set live_endpoint to your docker server address. Then netboot will look there for files.

https://netboot.xyz/docs/docker#local-mirror-access

@styxadmin
Copy link

styxadmin commented May 24, 2024

I know this is old, but by chance if found the key point to getting local assets working.

On dashboard, edit boot.cfg, and set live_endpoint to your docker server address. Then netboot will look there for files.

https://netboot.xyz/docs/docker#local-mirror-access

image

image

@danboid
Copy link
Contributor Author

danboid commented May 28, 2024

Thanks @DarkAxi0m! I've not tried this yet but will have to give it a go soon.

It would seem that the netboot maintainer had forgot how this was supposed to work. This should be added to the netboot docs.

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

No branches or pull requests

3 participants